Burning a data project to a dual layer TDK DVD+R 8X speed 8.5GB disk. Linux crashes right at the midpoint of the disk. Tried multiple disks, and different projects over a period of time. Using Brasero, the same project works fine on the same type TDK disk. Linux Ubuntu Studio 14.04. Updated to current. Quad core X64 system. 4GB ram. Processor and RAM both have a lot of head room, typically < 5% processor used, and <1.25GB ram used. No other applications running at the same time. K3B running as Root from terminal (SUDO). This acts like it will burn the first layer, then not the second. Burns a single layer disk fine. Reproducible: Always Steps to Reproduce: 1.Start K3B from terminal sudo k3b. 2.Put a TDK DVD+R dual layer DVD in Pioneer DVR-S18MBK 3.Start a new data project. 4.Highlight 7.8GB of 0.03 to 1.1 GB .jpg and .mov files, and drag and drop them to the project. 5. Start a burn 6.Burns to almost 4.0GB, then crashes the linux system, Mouse even freezes, have to shut down the system by holding down the power on button for 5 seconds. Actual Results: Just had to reboot as stated above, and scrap the disk. Expected Results: Burn 7.8GB data to disk, calculate checksum, then finalize disk. Disk then contains 7.8GV of .jpg and .mov files that can be viewed on Linux, and Windows systems. Had this problem with the previous motherboard in this box. The motherboard went bad, and was replaced with a Gigabit. Updated to new version of Ubuntu Studio, 14.04. Same problem with K3B, with both motherboards, and with previous version of Ubuntu Studio, and this version,14.04. Brasero 3.10.0 will burn the same files to a DVD from the same spindle on this system. K3B will burn a full single layer data disk project on this system, but not a dual layer. Also tried Philips DVD+R dual layer disks, same results.
First of all, K3B is designed to be able to be ran as a regular user. Do you have this same issue if you run as a user without sudo? Secondly, do you get any log messages in the system log or anything like that indicating what is causing the crash itself? Something like out of memory, or similar?
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!