Version: 1.65.0 (using KDE 4.2.4) OS: Linux Installed from: Mandriva RPMs At the completion of a burn, the app crashes, there is a brief part of the sound that announces the completion, but its cut off. I did see a similar report of this crash, but the end of the report suggested that the bug should be tested with a later version, namely 1.65.0, which is the version I have running. Attached is the trace that the app left... Application: K3b (k3b), signal SIGSEGV [Current thread is 1 (Thread 0xb467f6d0 (LWP 3187))] Thread 4 (Thread 0xb1f12b90 (LWP 3188)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb53244c1 in select () from /lib/i686/libc.so.6 #2 0xb5f9ad1c in ?? () from /usr/lib/libQtCore.so.4 #3 0xb5ec22e3 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb51c9315 in start_thread () from /lib/i686/libpthread.so.0 #5 0xb532c25e in clone () from /lib/i686/libc.so.6 Thread 3 (Thread 0xb0c1fb90 (LWP 3922)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb53244c1 in select () from /lib/i686/libc.so.6 #2 0xb7eb730c in ?? () from /usr/lib/libk3b.so.6 #3 0xb5ec22e3 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb51c9315 in start_thread () from /lib/i686/libpthread.so.0 #5 0xb532c25e in clone () from /lib/i686/libc.so.6 Thread 2 (Thread 0xb1711b90 (LWP 5895)): [KCrash Handler] #6 0xb7fd1ebe in K3b::Device::Track::firstSector () from /usr/lib/libk3bdevice.so.6 #7 0xb7ea627d in K3b::Medium::analyseContent () from /usr/lib/libk3b.so.6 #8 0xb7ea6835 in K3b::Medium::update () from /usr/lib/libk3b.so.6 #9 0xb7eaae59 in K3b::MediaCache::PollThread::run () from /usr/lib/libk3b.so.6 #10 0xb5ec22e3 in ?? () from /usr/lib/libQtCore.so.4 #11 0xb51c9315 in start_thread () from /lib/i686/libpthread.so.0 #12 0xb532c25e in clone () from /lib/i686/libc.so.6 Thread 1 (Thread 0xb467f6d0 (LWP 3187)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb51ccc45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb53398dd in pthread_cond_wait () from /lib/i686/libc.so.6 #3 0xb5ec33eb in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb5ec2491 in QThread::wait () from /usr/lib/libQtCore.so.4 #5 0xb7eb8be7 in ?? () from /usr/lib/libk3b.so.6 #6 0xb7eb9da8 in ?? () from /usr/lib/libk3b.so.6 #7 0xb527ccd9 in exit () from /lib/i686/libc.so.6 #8 0xb5618738 in ?? () from /usr/lib/libQtGui.so.4 #9 0xb64c7699 in KApplication::xioErrhandler () from /usr/lib/libkdeui.so.5 #10 0xb64c76d4 in ?? () from /usr/lib/libkdeui.so.5 #11 0xb4d340da in _XIOError () from /usr/lib/libX11.so.6 #12 0xb4d3c4fd in ?? () from /usr/lib/libX11.so.6 #13 0x09f5c0d8 in ?? () #14 0x00000000 in ?? ()
Merging with bug 195436. Thanks *** This bug has been marked as a duplicate of bug 195436 ***
SVN commit 1035785 by mmalek: Fixed GPF. Make sure Toc is not empty when analyzing DataContent medium. Although this situation should not happen for correct disks, it apparently happens sometimes (broken disk? failed burn? canceled burn?). Similar cause as in bug 204333. BUG: 210083 M +5 -2 k3bmedium.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1035785
*** Bug 215170 has been marked as a duplicate of this bug. ***
*** Bug 215173 has been marked as a duplicate of this bug. ***
*** Bug 215336 has been marked as a duplicate of this bug. ***
*** Bug 215549 has been marked as a duplicate of this bug. ***
*** Bug 215544 has been marked as a duplicate of this bug. ***