Bug 245159 - crash of k3b with image cue
Summary: crash of k3b with image cue
Status: RESOLVED DUPLICATE of bug 190775
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 1.68.0
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Michał Małek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-19 18:48 UTC by fabio tosarelli
Modified: 2010-07-26 20:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.69.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fabio tosarelli 2010-07-19 18:48:57 UTC
Application that crashed: k3b
Version of the application: 1.68.0
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-22-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I was burning an image cue and k3b closed.
I was also doing an upgrade of ubuntu.
I use K3b with gnome 3.

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

Thread 2 (Thread 0xb4581b70 (LWP 2623)):
#0  0x00867422 in __kernel_vsyscall ()
#1  0x00a9d142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x04a1ca04 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0x0536781e in ?? () from /usr/lib/libQtCore.so.4
#4  0x053679c0 in QThread::sleep(unsigned long) () from /usr/lib/libQtCore.so.4
#5  0x006bb2e9 in K3b::MediaCache::PollThread::run() () from /usr/lib/libk3b.so.6
#6  0x05367e32 in ?? () from /usr/lib/libQtCore.so.4
#7  0x00a9880e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x04a0fa0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb77f6920 (LWP 2490)):
[KCrash Handler]
#6  0x0070add8 in K3b::BinImageWritingJob::writerStart() () from /usr/lib/libk3b.so.6
#7  0x0070bc70 in K3b::BinImageWritingJob::start() () from /usr/lib/libk3b.so.6
#8  0x0070b11b in K3b::BinImageWritingJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libk3b.so.6
#9  0x05466f0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#10 0x054685fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#11 0x022f8f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#12 0x0230067c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#13 0x0201825a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#14 0x054586cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#15 0x054592b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#16 0x0545947d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#17 0x054833ff in ?? () from /usr/lib/libQtCore.so.4
#18 0x0669fe88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x066a3730 in ?? () from /lib/libglib-2.0.so.0
#20 0x066a3863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x0548302c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0x02399be5 in ?? () from /usr/lib/libQtGui.so.4
#23 0x05456c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0x054570ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0x027e5d53 in QDialog::exec() () from /usr/lib/libQtGui.so.4
#26 0x08189f18 in _start ()

Reported using DrKonqi
Comment 1 Nicolas L. 2010-07-19 19:50:19 UTC
Thread 1 (Thread 0xb77f6920 (LWP 2490)):
[KCrash Handler]
#6  0x0070add8 in K3b::BinImageWritingJob::writerStart() () from
/usr/lib/libk3b.so.6
#7  0x0070bc70 in K3b::BinImageWritingJob::start() () from /usr/lib/libk3b.so.6
#8  0x0070b11b in K3b::BinImageWritingJob::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib/libk3b.so.6


Please install the debuginfo package for k3b and kdelibs and then paste a new backtrace
Comment 2 Michał Małek 2010-07-26 20:12:24 UTC

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