| Summary: | K3B - Crash - "Fatal error during recording: input/output error" - at end of 21.2gb burn | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | pbea <2aq9j93b7s> |
| Component: | general | Assignee: | k3b developers <k3b> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | 2aq9j93b7s, idanan, ml-kdebugs, przemekkulczycki+kde, scdbackup, tgarson, trueg, zhaixiang |
| Priority: | NOR | ||
| Version: | 2.0.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
pbea
2011-09-11 18:07:14 UTC
I purged k3b and reinstalled it and tried another 25gb blu-ray disk. Both attempts were done with A1 quality blu-ray disks. The first a Philips BD-R 25gb and the second a Memorex BD-R 25gb disk. A second attempt at burning a blu-ray caused the same result. The first burn was 21.2gb and the second 12.1gb. The results were the same also a complete freeze and crash with no opportunity to capture any information. The following can now be added to the original report. Steps to Reproduce: Burn a blu-ray disk and it ends with the crash and freeze. Further info on the optical drive - PIONEER - BD-RW BDR-206 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 Got the same error on two burns yesterday except mine does not crash. The files are intact and a recursive diff (diff -qr <dir1> <blu-ray-dir>) does not return any errors. The system is OpenSUSE 12.2 64-bits fully update and using Verbatim 6X BD-R. Will try with TDK later. Same bug exists in Ubuntu and other distros: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/788322 64 bit Suse 13.1: K3B 98% done with burn of DVD and get I/O error, terminating burn. No crash. Twice in succession with Blu Ray but has been going on with DVDs as well. A search brought me to this bug report. I've now replaced cdrkit with latest cdrecord. Burn completed with no errors. Suse 13.1 Yast does require removal of cdrkit before install of cdrecord. I can confirm this on Debian Jessie, K3B 4.14.2, burning to a 4 GB dvd. *** This bug has been marked as a duplicate of bug 367639 *** quote from Thomas Schmitt is most probably the known growisofs bug about unformatted BD-R, which it formats automatically but then forgets to have done. An inappropriate CLOSE SESSION command is sent in the end and causes the error message. Diagnosis and fix are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016 Workaround: Add growisofs option -use-the-force-luke=spare=none if the BD-R medium is detected as blank. Or run dvd+rw-format on the BD-R before running growisofs. Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, 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 error I experienced a long time ago when I commented on the bug, but I am not the one to report it originally. It is no longer occurring now, but I no longer have the original hardware where that occurred. Either it is fixed or the problem is related to the old hardware. 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! |