Version: 0.11 (using KDE KDE 3.1.4) Installed from: RedHat RPMs OS: Linux When I select multiple files in the project pane and remove them by pressing delete or selecting remove from the menu, K3b crashes. Removing a single file works. This happens both with a self compiled version and the FC1 rpms. Sorry, no stack trace - my gdb is busted at the moment.
please provide some more informations: which type of project for example.
It happens with both Data DVD and CD projects. It only seems to happen for files, not directories, and only if you aren't deleting them all. I managed to get a stack trace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1108239424 (LWP 30906)] 0x40f825ad in __dynamic_cast () from /usr/lib/libstdc++.so.5 (gdb) bt #0 0x40f825ad in __dynamic_cast () from /usr/lib/libstdc++.so.5 #1 0x406dde07 in K3bDataFileView::slotRemoveItem() () from /usr/lib/libk3bproject.so.1 #2 0x406de2b7 in K3bDataFileView::qt_invoke(int, QUObject*) () from /usr/lib/libk3bproject.so.1 #3 0x4121e6cc in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #4 0x4121e504 in QObject::activate_signal(int) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #5 0x40b7661b in KAction::activated() () from /usr/lib/libkdeui.so.4 #6 0x40b6798f in KAction::slotActivated() () from /usr/lib/libkdeui.so.4 #7 0x40b76821 in KAction::qt_invoke(int, QUObject*) () from /usr/lib/libkdeui.so.4 #8 0x4121e6cc in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #9 0x4121e504 in QObject::activate_signal(int) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #10 0x40db1f3b in KAccelPrivate::menuItemActivated() () from /usr/lib/libkdecore.so.4 #11 0x40db07dc in KAccelPrivate::eventFilter(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #12 0x4121c25e in QObject::activate_filters(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #13 0x4121c18c in QObject::event(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #14 0x412535af in QWidget::event(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #15 0x40b940f2 in KListView::event(QEvent*) () from /usr/lib/libkdeui.so.4 #16 0x411c2faf in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #17 0x411c2aae in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #18 0x40d45c0a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #19 0x40daf774 in KAccelEventHandler::x11Event(_XEvent*) () from /usr/lib/libkdecore.so.4 #20 0x40d4ae3f in KApplication::x11EventFilter(_XEvent*) () from /usr/lib/libkdecore.so.4 #21 0x4114fe68 in qt_set_x11_event_filter(int (*)(_XEvent*)) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #22 0x4115968b in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #23 0x4116f9f1 in QEventLoop::processEvents(unsigned) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #24 0x411d66d8 in QEventLoop::enterLoop() () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #25 0x411d6588 in QEventLoop::exec() () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #26 0x411c3201 in QApplication::exec() () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #27 0x0809f16f in QPtrList<K3bPluginFactory>::deleteItem(void*) () #28 0x418047e0 in __libc_start_main () from /lib/tls/libc.so.6 #29 0x0807cea1 in ?? ()
Created attachment 4352 [details] Testcase (K3b Project)
Steps to reproduce the crash (well for me at least): 1. Unpack testcase to /tmp 2. Open test.k3b in k3b 3. Select all files in the project 4. Press delete or select remove from context menu Crashes 100% here.
I'm using K3b 0.10.3 with KDE 3.1-RC1 and I can't reproduce the crash. Would this be version 0.11 specific crash? (and i'm using gentoo packages)
.. and i mean that i'm using kde 3.2-rc1 :)
Yes, I think its 0.11 specific - It didn't happen before my upgrade. The only other thing that changed on my system lately which might be relevant is libstdc++ (libstdc++-3.3.2-7 from FC1+ atm).
I just upgraded to kde 3.2 (fc1 rpms) and K3b 11.1 and I still can crash it with the testcase.
==22262== Invalid read of size 4 ==22262== at 0x41E497C9: __dynamic_cast (in /usr/lib/libstdc++.so.5.0.5) ==22262== by 0x408FD0ED: K3bDataFileView::slotRemoveItem() (k3bdatafileview.cpp:314) ==22262== by 0x408FD4B7: K3bDataFileView::qt_invoke(int, QUObject*) (k3bdatafileview.moc:151) ==22262== by 0x4161A94A: QObject::activate_signal(QConnectionList*, QUObject*) (qobject.cpp:2359) ==22262== by 0x4161A7E9: QObject::activate_signal(int) (qobject.cpp:2328) <snip> ==22262== Address 0x46E8471C is 0 bytes inside a block of size 60 free'd ==22262== at 0x4002A0B3: __builtin_delete (vg_replace_malloc.c:244) ==22262== by 0x4002A0D1: operator delete(void*) (vg_replace_malloc.c:253) ==22262== by 0x409144AF: K3bDataFileViewItem::~K3bDataFileViewItem() (k3bdataviewitem.h:82) ==22262== by 0x41705FEB: QListView::clear() (qlistview.cpp:3211) ==22262== by 0x40837A24: K3bListView::clear() (k3blistview.cpp:484) ==22262== by 0x408FBABE: K3bDataFileView::updateContents() (k3bdatafileview.cpp:106) ==22262== by 0x408FD529: K3bDataFileView::qt_invoke(int, QUObject*) (k3bdatafileview.moc:145) ==22262== by 0x4161AA97: QObject::activate_signal(QConnectionList*, QUObject*) (qobject.cpp:2383) ==22262== by 0x4161A7E9: QObject::activate_signal(int) (qobject.cpp:2328) ==22262== by 0x408C9D24: K3bDoc::changed() (qmetaobject.h:261) ==22262== by 0x4090CC59: K3bDataDoc::removeItem(K3bDataItem*) (k3bdatadoc.cpp:1036) ==22262== by 0x408FD114: K3bDataFileView::slotRemoveItem() (k3bdatafileview.cpp:315)
Fixed in CVS HEAD.
it is not fixed. You simply commited a terrible HACK which fixes only one special case. :(
The same things happens to me, Here is data from a backtrace: 0x4196103b in waitpid () from /lib/libpthread.so.0 #0 0x4196103b in waitpid () from /lib/libpthread.so.0 #1 0x40f67c34 in ?? () from /usr/kde/3.2/lib/libkdecore.so.4
Hi, I haven't filed a bug report before so I hope this is right... I am getting the same problem removing multiple files that have been selected already in the lower cd pane. Using Gentoo 1.4, kde 3.2, 2.6.3 kernel, k3b 0.11. heres the stack trace: (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 7151)] 0x4179f5b8 in waitpid () from /lib/libpthread.so.0 #0 0x4179f5b8 in waitpid () from /lib/libpthread.so.0 #1 0x40f0fccc in ?? () from /usr/kde/3.2/lib/libkdecore.so.4 #2 0x40e4fff1 in KCrash::defaultCrashHandler(int) () from /usr/kde/3.2/lib/libkdecore.so.4 Hope this is some help to you. Regards Wayne.
what about k3b 0.11.9?
I can't reproduce the crash with k3b 0.11.9 (using kde 3.2.2).
i think this bug can be close as the reporter can't reproduce this bug
Closing this bug because it can probably be fixed by one of the below: 1. installing a new version of K3b 2. installing a new version of the cdrtools 3. Using a lower writing speed 4. using a different writing mode 5. using a different media brand. If none of the above help and closing this bug was a fault, please reopen.