Bug 223362 - Launching k3b to copy disc [K3b::Iso9660Directory::expand, K3b::Iso9660Directory::entry, K3b::Medium::analyseContent]
Summary: Launching k3b to copy disc [K3b::Iso9660Directory::expand, K3b::Iso9660Direct...
Status: RESOLVED FIXED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 1.69.0
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 196901 225108 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-19 02:46 UTC by Michael
Modified: 2010-02-01 22:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2010-01-19 02:46:53 UTC
Application that crashed: k3b
Version of the application: 1.69.0
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.6.0
Operating System: Linux 2.6.32-sabayon x86_64
Distribution: "Gentoo Base System release 2.0.1"

What I was doing when the application crashed:
when launching k3b from the device launcher (kde4) which displays copy with k3b, k3b segfaults

 -- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.3-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[Current thread is 1 (Thread 0x7f78a3ce8750 (LWP 13531))]

Thread 2 (Thread 0x7f788d3d1910 (LWP 13551)):
[KCrash Handler]
#5  0x00007f78a358e706 in K3b::Iso9660Directory::expand() () from /usr/lib64/libk3b.so.6
#6  0x00007f78a358ed45 in K3b::Iso9660Directory::entry(QString const&) () from /usr/lib64/libk3b.so.6
#7  0x00007f78a35ae7eb in K3b::Medium::analyseContent() () from /usr/lib64/libk3b.so.6
#8  0x00007f78a35aee4c in K3b::Medium::update() () from /usr/lib64/libk3b.so.6
#9  0x00007f78a35b02cc in K3b::MediaCache::PollThread::run() () from /usr/lib64/libk3b.so.6
#10 0x00007f789f8a11e5 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#11 0x00007f789e1b6624 in start_thread () from /lib/libpthread.so.0
#12 0x00007f789e6fc56d in clone () from /lib/libc.so.6
#13 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f78a3ce8750 (LWP 13531)):
#0  0x00007f789e6f38a3 in poll () from /lib/libc.so.6
#1  0x00007f789867eb4a in ?? () from /usr/lib/libxcb.so.1
#2  0x00007f789867f087 in ?? () from /usr/lib/libxcb.so.1
#3  0x00007f789867f335 in xcb_writev () from /usr/lib/libxcb.so.1
#4  0x00007f789c8cd35a in _XSend () from /usr/lib64/libX11.so.6
#5  0x00007f789c8cd499 in _XReply () from /usr/lib64/libX11.so.6
#6  0x00007f789c8aa867 in XGetWindowProperty () from /usr/lib64/libX11.so.6
#7  0x00007f789c8a99ac in XGetWMHints () from /usr/lib64/libX11.so.6
#8  0x00007f789eedde42 in QWidgetPrivate::show_sys() () from /usr/lib64/qt4/libQtGui.so.4
#9  0x00007f789eea08ed in QWidgetPrivate::show_helper() () from /usr/lib64/qt4/libQtGui.so.4
#10 0x00007f789eea25aa in QWidget::setVisible(bool) () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007f789f2b493c in QDialog::setVisible(bool) () from /usr/lib64/qt4/libQtGui.so.4
#12 0x00007f789f2b419a in QDialog::exec() () from /usr/lib64/qt4/libQtGui.so.4
#13 0x000000000055690d in _start ()

Reported using DrKonqi
Comment 1 Jonathan Thomas 2010-01-19 03:21:37 UTC
Looks similar to bug 196901.
Comment 2 Michael 2010-01-19 04:46:03 UTC
Extra details: I had just finished burning an iso, which I think failed as i cant access the disc and that may be what is causing the crash.
Comment 3 Michael 2010-01-19 04:49:13 UTC
version 1.69.0
Comment 4 Michał Małek 2010-01-19 08:01:03 UTC
SVN commit 1076951 by mmalek:

Additional checking if firstIsoDirEntry is not null. It might happen e.g. after failed burn.
BUG: 223362

 M  +34 -29    k3bmedium.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1076951
Comment 5 Michał Małek 2010-01-19 08:02:16 UTC
*** Bug 196901 has been marked as a duplicate of this bug. ***
Comment 6 Dario Andres 2010-02-01 22:24:39 UTC
*** Bug 225108 has been marked as a duplicate of this bug. ***