Version: 1.0.2 (using KDE KDE 3.5.7) Installed from: Unlisted Binary Package Compiler: gcc-4.2-20070620-1 OS: Linux I'm one of the developer of Paldo GNU/Linux (paldo.org). Now I've the problem that the latest stable version of k3b 1.0.2 crashes on my system on both archs. You can read my forum post here: http://forum.paldo.org/index.php?action=topic&topicnr=225 Also I did a package of the svn version r681398: http://www.paldo.org/~amnon/repo/sources/k3b/k3b-1.1-r681398.tar.bz2 http://www.paldo.org/~amnon/repo/specs/k3b.xml I can see this last lines in the terminal: (K3bDevice::Device) /dev/sr0: dataLen: 60 (K3bDevice::Device) /dev/sr0: checking for TAO (K3bDevice::Device) /dev/sr0: checking for SAO (K3bDevice::Device) /dev/sr0: checking for SAO_R96P (K3bDevice::Device) /dev/sr0: checking for SAO_R96R (K3bDevice::Device) /dev/sr0: checking for RAW_R16 (K3bDevice::Device) /dev/sr0: checking for RAW_R96P (K3bDevice::Device) /dev/sr0: checking for RAW_R96R Then my pc freezes and crashes. A normal start of k3b 1.0.1 looked like this: http://pastebin.ca/592717 What happend? How can I fix it? These are the files of 1.0.2: http://www.paldo.org/paldo/specs/k3b.xml http://www.paldo.org/paldo/sources/k3b/k3b-1.0.2.tar.bz2
I've a Linux Box powered by AMD 3800+ X2 CPU. My distro is a Slamd64 current. I've two serial ata HDs (raid0 software) and three optical drives: Plextor PX-716A, Plextor PX-755A, Optiarc AD-7371s SATA drive. The two ATA drives use the new libata interface. k3b 1.0.1 works fine. K3b 1.0.2 freezes completely the system when I start the program. The lock is very hard. No SSH is possible on the affected machine. Only hard reset is possible. In a case I got also a filesystem corruption
Seems this bug is related with this one: https://bugs.kde.org/show_bug.cgi?id=147676
were both 1.0.1 and 1.0.2 built the exact same way with the same settings? I ask because I did not change anything in the device handling code (at least nothing that should make K3b crash, ... well, should....)
Seems to me this bug is related with the "k3b-1.0.2 device offlined" bug: https://bugs.kde.org/show_bug.cgi?id=147611 If I start k3b with the usb dvd writer unplugged k3b and the plug it in, k3b stops responding until I unplug the dvd writer.
Created attachment 31137 [details] Text Document of an attempt to run K3B through Shell.
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED. If this bug is still valid for 2.0, please reopen it.