Version: (using KDE 4.2.3) Compiler: gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) OS: Linux Installed from: Gentoo Packages Steps to reproduce: 1) Delete some directory structure for good (Shift + del) [the directory thing seems to be important, as I can only "undo" the deletion of a file once] 2) Try to undo the delete process (CTRL+Z) 3) When asked if you really want to delete the items (!!!) that you want to restore, hit delete 4) Try to undo the delete process once again (CTRL+Z) 5) When asked if you really want to delete the items (!!!) that you want to restore, hit delete again 6) See a stalled notification about the deletion process pop up 7) Cancel the notification by hitting the cancel button 8) See dolphin (seems to be kdelibs really) crash with the backtrace below I also uploaded a video showing how to reproduce the bug at www.oliver-putz.de/bugreports/dolphinUndoDeletion.ogv Note: This looks similar to bug #192547, but as that one is about undoing the overriding of a file I open a new bugreport. In any case, the simple backtrace is: [Thread debugging using libthread_db enabled] [New Thread 0x7f3ffeedf750 (LWP 10869)] [KCrash handler] #5 0x00007f3ffca56d54 in KJob::kill (this=0x10ee030, verbosity=KJob::EmitResult) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kdecore/jobs/kjob.cpp:106 #6 0x00007f3ffd184e79 in KUiServerJobTracker::qt_metacall (this=0x10b8390, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff06f21c90) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kdeui/kuiserverjobtracker.moc:93 #7 0x00007f3ffc473900 in QMetaObject::activate (sender=0x109be70, from_signal_index=<value optimized out>, to_signal_index=5, argv=0x10ecd10) at kernel/qobject.cpp:3025 #8 0x00007f3ffd262aa1 in OrgKdeJobViewInterface::qt_metacall ( this=0x109be70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff06f220a0) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kdeui/jobviewiface.moc:89 #9 0x00007f3ffc74e6bb in QDBusConnectionPrivate::deliverCall (this=0x680ca0, object=0x109be70, msg=@0x10b8f88, metaTypes=@0x10b8f90, slotIdx=5) at qdbusintegrator.cpp:855 #10 0x00007f3ffc75547f in QDBusCallDeliveryEvent::placeMetaCall (this=0x0, object=0x1) at qdbusintegrator_p.h:136 #11 0x00007f3ffc46d73e in QObject::event (this=0x109be70, e=0x10b8f40) at kernel/qobject.cpp:1149 #12 0x00007f3ffb81aa2d in QApplicationPrivate::notify_helper (this=0x68c7e0, receiver=0x109be70, e=0x10b8f40) at kernel/qapplication.cpp:3809 #13 0x00007f3ffb821d8e in QApplication::notify (this=0x7fff06f22c80, receiver=0x109be70, e=0x10b8f40) at kernel/qapplication.cpp:3774 #14 0x00007f3ffd188f84 in KApplication::notify (this=0x7fff06f22c80, receiver=0x109be70, event=0x10b8f40) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kdeui/kernel/kapplication.cpp:307 #15 0x00007f3ffc45ebe0 in QCoreApplication::notifyInternal ( this=0x7fff06f22c80, receiver=0x109be70, event=0x10b8f40) at kernel/qcoreapplication.cpp:589 #16 0x00007f3ffc462493 in QCoreApplicationPrivate::sendPostedEvents ( receiver=0x0, event_type=0, data=0x66fd80) at kernel/qcoreapplication.h:215 #17 0x00007f3ffc485de3 in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:220 #18 0x00007f3ff7de8614 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x00007f3ff7dea4d7 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #20 0x00007f3ff7dea5bd in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x00007f3ffc485b1f in QEventDispatcherGlib::processEvents (this=0x68c3e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325 #22 0x00007f3ffb8a0e1f in QGuiEventDispatcherGlib::processEvents ( this=0x10ee030, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x00007f3ffc45d812 in QEventLoop::processEvents ( this=<value optimized out>, flags={i = 116534192}) at kernel/qeventloop.cpp:149 #24 0x00007f3ffc45d9a5 in QEventLoop::exec (this=0x7fff06f22bf0, flags= {i = 116534272}) at kernel/qeventloop.cpp:196 #25 0x00007f3ffc462747 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851 #26 0x000000000043addd in main (argc=5, argv=0x7fff06f23168) at /var/tmp/portage/kde-base/dolphin-4.2.3-r1/work/dolphin-4.2.3/dolphin/src/main.cpp:94
Created attachment 34228 [details] bt full log for crash from bug 195071 A full backtrace with "bt full" from gdb for this crash
This also reminds me bug 168427 a bit.
Thank you for the report, Oliver. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!