Bug 230322 - K3B crashed after trying to burn a .cue CD image
Summary: K3B crashed after trying to burn a .cue CD image
Status: RESOLVED DUPLICATE of bug 190775
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 1.68.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-11 14:46 UTC by Franck GOETHALS
Modified: 2010-03-11 14:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franck GOETHALS 2010-03-11 14:46:01 UTC
Application: k3b (1.68.0)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.31-20-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
This happens each time I try to burn a .cue CD image, no matter what .cue it is. I've seen a lot reports about the same problem, but there were some differences every time, that's why I'm sending my own report. I hope it will help.

The crash can be reproduced every time.

 -- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7808760 (LWP 964))]

Thread 2 (Thread 0xb5759b70 (LWP 983)):
#0  0x00528422 in __kernel_vsyscall ()
#1  0x00797142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x025ad8d4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0x022bac5e in ?? () from /usr/lib/libQtCore.so.4
#4  0x022bae00 in QThread::sleep(unsigned long) () from /usr/lib/libQtCore.so.4
#5  0x00d082e9 in K3b::MediaCache::PollThread::run() () from /usr/lib/libk3b.so.6
#6  0x022bb36e in ?? () from /usr/lib/libQtCore.so.4
#7  0x0079280e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x025a08de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7808760 (LWP 964)):
[KCrash Handler]
#6  0x00d57dd8 in K3b::BinImageWritingJob::writerStart() () from /usr/lib/libk3b.so.6
#7  0x00d58c70 in K3b::BinImageWritingJob::start() () from /usr/lib/libk3b.so.6
#8  0x00d5811b in K3b::BinImageWritingJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libk3b.so.6
#9  0x023c2e5a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x023cd516 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#11 0x023ce63e in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#12 0x08a1d3cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#13 0x08a2401e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#14 0x0207d42a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x023bdbeb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x023c0623 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#17 0x023c078d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#18 0x023e9d0f in ?? () from /usr/lib/libQtCore.so.4
#19 0x02b40e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#20 0x02b44730 in ?? () from /lib/libglib-2.0.so.0
#21 0x02b44863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#22 0x023e9805 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x08adcb35 in ?? () from /usr/lib/libQtGui.so.4
#24 0x023bc209 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0x023bc65a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0x08f5bba3 in QDialog::exec() () from /usr/lib/libQtGui.so.4
#27 0x08189f18 in _start ()

Possible duplicates by query: bug 225754, bug 224140, bug 222711, bug 221860, bug 221278.

Reported using DrKonqi
Comment 1 Michał Małek 2010-03-11 14:58:13 UTC
Fixed on K3b 1.69 (2.0-alpha4) or later

*** This bug has been marked as a duplicate of bug 190775 ***