Bug 387599 - K3B won't exit after copying
Summary: K3B won't exit after copying
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Copying (show other bugs)
Version: 17.08.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-04 18:34 UTC by Lloyd Osten
Modified: 2022-12-10 05:17 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lloyd Osten 2017-12-04 18:34:13 UTC
After burning an ISO file onto a Blu-ray disk, K3B refuses to close. I have to manually open a Konsole session to kill it. All other types of discs work fine.
Comment 1 Leslie Zhai 2017-12-05 05:25:09 UTC

*** This bug has been marked as a duplicate of bug 385667 ***
Comment 2 Thomas Schmitt 2017-12-05 08:54:28 UTC
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
Comment 3 Christoph Feck 2017-12-31 09:31:05 UTC
Clarified issue in title.
Comment 4 Justin Zobel 2022-11-10 22:32:53 UTC
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!
Comment 5 Bug Janitor Service 2022-11-25 05:20:21 UTC
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!
Comment 6 Bug Janitor Service 2022-12-10 05:17:05 UTC
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!