I'm observing the following issue: On my PC, which has an Asus M5A88-V EVO Mainboard, the whole system freezes completely (to a point where not even sysrq-keys work) nearly every time when I try to launch k3b. This happens on both, Ubuntu and Gentoo, both with k3b 2.0.2 and 2.0.2_p20140225. It is not caused by my optical drives, since the freeze also happens if these are disconnected from the mainboard. On some rare occasions k3b actually does start, but this is completely irreproducible. Sometimes the main window of k3b is shown behind the splash screen before the system freezes, most times the freeze occurs while just the splash screen is visible. Other CD-writing applications like Brasero work without issues. I've alredy tried to update to the latest BIOS version, with no change. The issue might be related to the VT6330 IDE controller present on the mainboard (actually, lspci lists it as VT6415). I'm willing to help investigate the issue, but unfortunately I don't know how to get reasonable information on what system call or whatever triggers the system freeze (I've tried "strace k3b", but that doesn't give any output...). The fact that the whole system freezes makes this whole thing rather annoying, since there is no easy way to copy&paste the command line output and also files are not written to disk. Two years ago I posted a bug report for Ubuntu regarding the same issue ( https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/880042 ), but since nothing changed meanwhile, I decided to repost here, upstream.
It could be a kernel crash caused by the burner device. I sent an email (in German) to the bug reporter with instructions to perhaps get a backtrace.
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!