Application that crashed: dolphin Version of the application: 1.3 KDE Version: 4.3.1 (KDE 4.3.1) "release 6" Qt Version: 4.5.3 Operating System: Linux 2.6.31.12-0.1-desktop x86_64 Distribution: "openSUSE 11.2 (x86_64)" What I was doing when the application crashed: Dolphin crashed when i changed directory. Shortly before i had moved three iso-images from one folder to another. During that action, i made a mistake, i wanted to move and pressed the "copy" action instead of the "move" (in the right mousebutton dropdownmenu). I discovered my mistake soon and cancelled it, then made the system do the mv-action. This went well, but when changing dirs Dolphin crashed. Crashreportassistant offers me to install debug-packets, but these are not available for my system. Feel free to contact me for additional information. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007f83cff1c2d0 in ?? () from /usr/lib64/libkio.so.5 #6 0x00007f83cff1c371 in ?? () from /usr/lib64/libkio.so.5 #7 0x00007f83cff20d16 in ?? () from /usr/lib64/libkio.so.5 #8 0x00007f83cff220f6 in KDirModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #9 0x00007f83ccf01fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x00007f83cff05e3a in KDirLister::itemsAdded(KUrl const&, KFileItemList const&) () from /usr/lib64/libkio.so.5 #11 0x00007f83cff06bea in KDirLister::Private::emitItems() () from /usr/lib64/libkio.so.5 #12 0x00007f83cff11688 in ?? () from /usr/lib64/libkio.so.5 #13 0x00007f83cff11ffe in ?? () from /usr/lib64/libkio.so.5 #14 0x00007f83cff18320 in ?? () from /usr/lib64/libkio.so.5 #15 0x00007f83ccf01fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #16 0x00007f83cff23695 in OrgKdeKDirNotifyInterface::FilesChanged(QStringList const&) () from /usr/lib64/libkio.so.5 #17 0x00007f83cff23800 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #18 0x00007f83cdd92b78 in ?? () from /usr/lib64/libQtDBus.so.4 #19 0x00007f83cdd9a16f in ?? () from /usr/lib64/libQtDBus.so.4 #20 0x00007f83ccefc2d9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #21 0x00007f83cd37d2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #22 0x00007f83cd38457e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #23 0x00007f83ce6618d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #24 0x00007f83cceecddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #25 0x00007f83cceed9ea in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #26 0x00007f83ccf15803 in ?? () from /usr/lib64/libQtCore.so.4 #27 0x00007f83c8a36dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f83c8a3a7b8 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f83c8a3a8e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f83ccf153a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007f83cd41031e in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007f83cceeb712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #33 0x00007f83cceebae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007f83cceedc99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #35 0x0000000000439575 in _start () This bug may be a duplicate of or related to bug 206008 Reported using DrKonqi
Thanks for the bug report! The visible parts of the backtrace look very much like it's a duplicate of bug 190535. This crash is partly fixed in KDE 4.3.5 and later. > Feel free to contact me for additional information. If you upgrade to KDE 4.4 one day and still find a way to reproduce this crash reliably, that would help a lot! Thanks! *** This bug has been marked as a duplicate of bug 190535 ***