| Summary: | K3B won't exit after copying | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Lloyd Osten <lloyd.osten> |
| Component: | Copying | Assignee: | k3b developers <k3b> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bugseforuns, lloyd.osten, michalm, scdbackup, trueg, zhaixiang |
| Priority: | NOR | ||
| Version: | 17.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Lloyd Osten
2017-12-04 18:34:13 UTC
*** This bug has been marked as a duplicate of bug 385667 *** Hi, i doubt that this is a duplicate of bug 385667. It could be a consequence of the known growisofs bug at the end of a burn run to a previously blank BD-R medium: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679 This bug is supposed not to damage the burn result, because the failed SCSI transaction was not necessary. But it will cause growisofs to return with non-zero exit value and thus make K3B believe that the burn run failed. The fix in the Debian bug report is tiny. If you have growisofs source code then consider to apply it. Else urge your distro maintainers to apply it to their growisofs package. As workaround you could format the BD-R medium by program dvd+rw-format before you give it to growisofs for burning. This will cause growisofs to omit the offending SCSI transaction. Have a nice day :) Thomas Clarified issue in title. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |