Version: unspecified (using Devel) OS: Linux k3b2.0 crashes with error whhile burning blu ray discs. It proceeds upto 99/% done, before reporting "Fatal error during recording: Input/Output error" The error log does not seem to suggest this though. (attached) OS : opensuse11.2 System ----------------------- K3b Version: 2.0.0 KDE Version: 4.4.5 (KDE 4.4.5) "release 272" QT Version: 4.6.3 Kernel: 2.6.31.5-0.1-xen Used versions ----------------------- mkisofs: 1.1.9 growisofs: 7.1 Reproducible: Didn't try Actual Results:
Created attachment 49133 [details] Error Log
I'm using K3B V2.0.1 on Ubunutu 10.10 and receive the same error message. I don't find that K3B crashes, it only reports an error, although there is no evidence of this error in the log file that I can see. The error seems to occur roughly when the disc is being "closed", but I can't be sure of this.
I'm using the same K3b V2.0.1 on Ubuntu 10.10 of #2 and I receive the same error message at 99%. I confirm that the error occurr when the "writing" part is done: I checked the MD5 hash of every burned file and they are all ok (and i didn't get any io error either) I have a LG bh10ls30.
After some digging and experimenting I have found the following which I hope may of help to other people in a similar predicament... Problem caused by cdrecord (http://cdrecord.berlios.de/) licensing issues and past feuds which result in cdrkit (http://www.cdrkit.org/) being installed on system (Debian, Ubuntu, Suse, etc) and used in place of actual cdrecord binaries. cdrkit binaries based on old and buggy code. k3b patched to detect cdrkit installation and use growisofs instead - https://git.reviewboard.kde.org/r/101208/. In referenced bugs growisofs seems to have an issue closing the BD-R session resulting in the last file burnt to the disc being faulty and the disc left open ("Appendable: yes" in k3b after burning). Solution is to install cdrecord. Removal of cdrkit isn't required as k3b will detect cdrecord from default install path of /opt/schily/. For installation instructions on Debian-based O/S see: http://ubuntuforums.org/showpost.php?p=5552555&postcount=5 Note that you can stop at 'sudo make install' in the above and k3b will find cdrecord, no adjusting with symlinks in /usr/bin is required. Apparently as detailed in http://forum.kde.org/viewtopic.php?f=153&t=85895&start=15#p165603 - setting k3b to "No Multisession" will cause it to use cdrecord instead of growisofs. Have tested the above on Debian Wheezy. Good luck - Ben Whorwood (mube.co.uk) === Issue referenced in bugs... http://forum.kde.org/viewtopic.php?f=153&t=85895&sid=f3d37339bce3fcc5d907daea285e98a6&start=15 https://bugs.kde.org/show_bug.cgi?id=281818 https://bugs.kde.org/show_bug.cgi?id=244549 https://bugs.kde.org/show_bug.cgi?id=257652 === Solution based on... https://bugzilla.novell.com/show_bug.cgi?id=656502 https://git.reviewboard.kde.org/r/101208/ http://ubuntuforums.org/showthread.php?t=851707
I am using K3b v. 1.0.5 on a Centos 6.4 platform. When I try to burn a blu-ray disc of 20gb of data, the software knowledges the disc is loaded, but it will not burn to disc.
Can you guys attach the backtrace shown by Dr Konqi?
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 set the bug status 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!
Dear Bug Submitter, 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!