Summary: | K3B doesn't close Blu-ray discs correctly | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Lloyd Osten <lloyd.osten> |
Component: | Copying | Assignee: | k3b developers <k3b> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | bugseforuns, lloyd.osten, michalm, scdbackup, trueg, zhaixiang |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mageia RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Lloyd Osten
2017-10-12 18:19:34 UTC
Hi Lloyd, v2.10.0 was not be maintained any more, please use K3b v17.08 https://github.com/KDE/k3b Regards, Leslie Zhai I'm thinking it's a problem with GROWISOFS. This problem has been around for a while. It also fails using openSUSE and Fedora Core 27. Version 17.08 still has this problem Hi Thomas, Please help Lloyd to debug GROWISOFS, thanks a lot! Regards, Leslie Zhai *** Bug 387599 has been marked as a duplicate of this bug. *** Hi, i cannot find the message text "APPENDABLE DATA ERROR" in the current K3B source. Please post the original message. Also please post the output of program run dvd+rw-mediainfo /dev/sr0 when one of the problematic BD-R media is inserted. (I assume that your drive has address /dev/sr0. If you have more than one, then it could be /dev/sr1, /dev/sr2, ...) If you burn some BD-R medium again, then please ishow the growisofs command line, which K3B used, and the other debug messages. ------------------------------------------------------------------------ growisofs keeps most media types appendable by default. But afaik, K3B adds options like -dvd-compat which would cause closing of the medium. There is a bug in original growisofs about the end of a BD-R burn run. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 But that is supposed not to spoil the medium but to only let growisofs report failure to its caller. (Thus i deem it a candidate for bug 387599.) Have a nice day :) Thomas If you can provide the information requested in comment #5, please add it. To further investigate this issue, KDE developers need the information requested in comment #5. If you can provide it, or need help with finding that information, please add a comment. No response; changing status. If you have new information, please add a comment. |