Hello,

the only feature I'm missing in k3b is the ability to remove/hide files from previous sessions. It's not about hiding from jouliet or RR but from the ISO9660. Also trying to rename a file from the old session does not work.

btw it is hard to write new session without importing the previous one. There is some problem with "do not import previous session" in custom filesystem options. I check it but then opening options again, it shows unchecked. I notice that if I then choose Custom from the drop down list the option applies.

Any chances these could be fixed?

P.S. using k3b 2.0.1 from debian.

In general, the best place for bug reports is bugs.kde.org. (the lack of retention of that option is a bug - if the option is not possible it should be disabled at the very least)

viewtopic.php?f=15&t=107290&p=247897#p247897

l.t. wrote:viewtopic.php?f=15&t=107290&p=247897#p247897

That makes very little sense to the user. How many hours would user need to compile k3b+kde to report a bug? It's prohibitively hard and I don't think you can reasonably expect it if user is not already on the latest version. And how many users can track the latest version?

On the other hand this is OSS and I can understand developers' frustration, because they often donate a lot of their time to the project. But still it is the developer that can really make a difference in this situation. So if developer does not have enough time (or does not want to verify bugs are still present on latest build), he/she could write instructions to the users how to build and try the latest version of the project in a non-destructive to the user's OS way. Also there could be VNC access to machines with preinstalled latest version of project to try. These machines could be rebuild every day to fix any damages caused by malicious/careless users. In the case of k3B the latter could hardly work well though.

@avalon: In this case, some of the problems you are seeing are the result of a fork (due to percieved license issues by some distributions). The original code in this case functions differently and has seen more development than the fork.

bcooksley wrote:@avalon: In this case, some of the problems you are seeing are the result of a fork (due to percieved license issues by some distributions). The original code in this case functions differently and has seen more development than the fork.

@bcooksley, could you point me at any resources about this/these fork(s)? Looking at debian sources [1] I can't see any serious patches to upstream that would affect removing files from previous sessions. Or perhaps I fail to notice them?

[1] http://packages.debian.org/source/stable/k3b , http://packages.debian.org/source/sid/k3b

The forks concern cdrtools, et. al, the underlying tools used by K3b to burn discs.

bcooksley wrote:The forks concern cdrtools, et. al, the underlying tools used by K3b to burn discs.

Ah, makes sense wrt forcing import of the session, I have to take a look. What about removing files from old session, is this possible in k3b upstream?

Unfortunately I do not have a rewritable disc available to test with at the moment. You could try asking the K3b developers however, details on contacting them can be found on the website at http://k3b.kde.org/