Hi Michael, > you may have noticed the bug was already known and so our bug was marked > as a duplicate. See http://bugs.kde.org/show_bug.cgi?id=144032
Thanks for pointing that out, I hadn't noticed actually. Normally, I get an email from bugzilla about such things. Weird. > It seems it is solved there. The k3b svn is fixed and users reported > success with version svn-1.40-29 or 1.1svn (I don't get that version > difference there exactly). So, what now? Should I try to apply the > patch / install from svn, or should I just wait? Well, it sounds like it will be in the next release of K3b so that should solve your problem whenever it gets released, but I don't know when that will be. If you prefer to do something now, feel free to apply the patch yourself and test it out and tell me about the results here. I can't reproduce the problem myself, but if you are successful with a patch against the current Debian package, I may release a new version of the package (with your patch) before the next upstream release. Although before you do this work, you may want to check with the main K3b developer whether or not he has plans to release the next version of K3b soon. Cheers, Francois -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
