Bug 230340 - Crash when canceling hung/failed move progress window
Summary: Crash when canceling hung/failed move progress window
Status: RESOLVED NOT A BUG
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: SVN
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 245552 277571 280782 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-11 17:48 UTC by Christoph Feck
Modified: 2013-07-09 12:19 UTC (History)
7 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 Christoph Feck 2010-03-11 17:48:11 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.67 (KDE 4.4.67 (KDE 4.5 >= 20100310)) (Compiled from sources)
Qt Version: 4.6.3
Operating System: Linux 2.6.31.12-0.1-desktop i686
Distribution: "openSUSE 11.2 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I moved a folders content to a different location, then deleted the empty source folder. Then I decided to undo the move operation. This failed, because the old folder was already deleted, and an error message was displayed in status bar. The (non plasma, i.e. old style) progress window did, however, not go away automatically. I clicked cancel there and got this crash. I tried to reproduce this with a simple test move, and it is always reproducable.


The crash can be reproduced every time.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#7  0x08165a68 in ?? ()
#8  0xb6cec933 in KAbstractWidgetJobTracker::slotStop (this=0x851dde8, job=0x8721ed8) at /local/svn/kde/trunk/KDE/kdelibs/kdeui/jobs/kabstractwidgetjobtracker.cpp:80
#9  0xb6ceff47 in KWidgetJobTracker::Private::ProgressWidget::_k_stop (this=0x8578ff8) at /local/svn/kde/trunk/KDE/kdelibs/kdeui/jobs/kwidgetjobtracker.cpp:645
#10 0xb6cf075f in KWidgetJobTracker::Private::ProgressWidget::qt_metacall (this=0x8578ff8, _c=InvokeMetaMethod, _id=13, _a=0xbfe640f8) at /local/build/KDE/kdelibs/kdeui/kwidgetjobtracker_p.moc:109
#11 0xb66774fd in QMetaObject::metacall (object=0x8578ff8, cl=3067005198, idx=40, argv=0xbfe640f8) at kernel/qmetaobject.cpp:237
#12 0xb6686720 in QMetaObject::activate (sender=0xbca03d0, m=0xb64dc944, local_signal_index=2, argv=0xbfe640f8) at kernel/qobject.cpp:3287
#13 0xb62d41cd in QAbstractButton::clicked (this=0xbca03d0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206
#14 0xb5f9faed in QAbstractButtonPrivate::emitClicked (this=0x90d29c8) at widgets/qabstractbutton.cpp:546
#15 0xb5fa0a3b in QAbstractButtonPrivate::click (this=0x90d29c8) at widgets/qabstractbutton.cpp:539
#16 0xb5fa0cf6 in QAbstractButton::mouseReleaseEvent (this=0xbca03d0, e=0xbfe64800) at widgets/qabstractbutton.cpp:1121
#17 0xb5c06e4b in QWidget::event (this=0xbca03d0, event=0xbfe64800) at kernel/qwidget.cpp:8038
#18 0xb5f9f980 in QAbstractButton::event (this=0xbca03d0, e=0x8165a68) at widgets/qabstractbutton.cpp:1080
#19 0xb604d268 in QPushButton::event (this=0xbca03d0, e=0xbfe64800) at widgets/qpushbutton.cpp:679
#20 0xb5ba61fc in QApplicationPrivate::notify_helper (this=0x811db68, receiver=0xbca03d0, e=0xbfe64800) at kernel/qapplication.cpp:4300
#21 0xb5bad9fe in QApplication::notify (this=0xbfe64534, receiver=0xbca03d0, e=0xbfe64800) at kernel/qapplication.cpp:3865
#22 0xb6cf7f90 in KApplication::notify (this=0xbfe65044, receiver=0xbca03d0, event=0xbfe64800) at /local/svn/kde/trunk/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302
#23 0xb667211e in QCoreApplication::notifyInternal (this=0xbfe65044, receiver=0xbca03d0, event=0xbfe64800) at kernel/qcoreapplication.cpp:704
#24 0xb5bac944 in sendSpontaneousEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:218
#25 QApplicationPrivate::sendMouseEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qapplication.cpp:2963
#26 0xb5c3a5ea in QETWidget::translateMouseEvent (this=0x8578ff8, event=0xbfe64d0c) at kernel/qapplication_x11.cpp:4380
#27 0xb5c39b94 in QApplication::x11ProcessEvent (this=0xbfe65044, event=0xbfe64d0c) at kernel/qapplication_x11.cpp:3391
#28 0xb5c67008 in x11EventSourceDispatch (s=0x812a270, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#29 0xb51564c2 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#30 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#31 0xb5159d98 in g_main_context_iterate (context=0x8129698, block=<value optimized out>, dispatch=1, self=0x811da00) at gmain.c:2591
#32 0xb5159ebe in IA__g_main_context_iteration (context=0x8129698, may_block=1) at gmain.c:2654
#33 0xb669ed21 in QEventDispatcherGlib::processEvents (this=0x811bfe0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#34 0xb5c66b5a in QGuiEventDispatcherGlib::processEvents (this=0x811bfe0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0xb667078d in QEventLoop::processEvents (this=0xbfe64fc4, flags=) at kernel/qeventloop.cpp:149
#36 0xb6670bd9 in QEventLoop::exec (this=0xbfe64fc4, flags=...) at kernel/qeventloop.cpp:201
#37 0xb6675e50 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#38 0xb5ba62a4 in QApplication::exec () at kernel/qapplication.cpp:3579
#39 0x0807cb0c in main (argc=5, argv=0xbfe65214) at /local/svn/kde/trunk/KDE/kdebase/apps/dolphin/src/main.cpp:101

This bug may be a duplicate of or related to bug 168427.

Possible duplicates by query: bug 168691, bug 168427, bug 166157, bug 159206.

Reported using DrKonqi
Comment 1 Dario Andres 2010-03-14 13:46:08 UTC
Yes, it mostly looks like my old bug 168427.
Comment 2 Frank Reininghaus 2010-09-26 23:56:13 UTC
*** Bug 245552 has been marked as a duplicate of this bug. ***
Comment 3 Frank Reininghaus 2011-07-12 11:23:34 UTC
*** Bug 277571 has been marked as a duplicate of this bug. ***
Comment 4 Frank Reininghaus 2011-08-26 15:18:20 UTC
*** Bug 280782 has been marked as a duplicate of this bug. ***
Comment 5 Dawit Alemayehu 2013-07-07 11:32:25 UTC
Is this still an issue in KDE v4.10?
Comment 6 Christoph Feck 2013-07-07 17:54:44 UTC
I can no longer activate the (non plasma, i.e. old style) progress window (unchecking the "File transfers and jobs" in the Notification Settings does not make it appear), so I guess this bug went "out of scope".
Comment 7 Dawit Alemayehu 2013-07-07 21:47:37 UTC
Since we have no "out of scope" status, resolving this as INVALID.  Thanks Christoph.
Comment 8 David Faure 2013-07-09 12:19:26 UTC
Well, the use of separate progress windows still happens if plasma isn't running.

(and I consider the removal of the option a bug in itself...)