Bug 172171

Summary: Deleting file dialog hangs, when closed crashes Dolphin
Product: [Unmaintained] kdelibs Reporter: Timothy Johnston <hattable+bugs>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aseigo, phil
Priority: NOR    
Version: 4.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Timothy Johnston 2008-10-05 01:09:34 UTC
Version:            (using KDE 4.1.1)
Installed from:    Ubuntu Packages

When deleting any files in groups or one by one, ever 3 or 4 delete operations will have the 'deleting - process' dialog box hang with no information and only about 10% of the process-completed bar finished. Dolphin remains usable but if you click [Cancel] or the close [X] all of Dolphin Crashes. It _seems_ more frequent when the file operations are on an external hard drive.

Backtrace:

<lot of no symbols found>



[Thread debugging using libthread_db enabled]
[New Thread 0xb63a4720 (LWP 30405)]
[New Thread 0xb4d43b90 (LWP 30406)]



<more no symbols found>



[KCrash handler]
#6  0xb7d0d9af in KJob::kill () from /usr/lib/kde4/lib/libkdecore.so.5
#7  0xb7ae3df6 in KAbstractWidgetJobTracker::slotStop ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#8  0xb7ae646e in KWidgetJobTracker::Private::ProgressWidget::closeEvent ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#9  0xb702efbd in QWidget::event () from /usr/lib/libQtGui.so.4
#10 0xb6fe528d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#11 0xb6fe8c4c in QApplication::notify () from /usr/lib/libQtGui.so.4
#12 0xb7af1ce3 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#13 0xb7efcc1b in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#14 0xb7029d86 in QWidgetPrivate::close_helper () from /usr/lib/libQtGui.so.4
#15 0xb7034058 in ?? () from /usr/lib/libQtGui.so.4
#16 0xb7035018 in QApplication::x11ClientMessage ()
   from /usr/lib/libQtGui.so.4
#17 0xb70406d9 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#18 0xb7066684 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb6aaddd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb6ab1193 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb6ab174e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb7f20f82 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#23 0xb7066475 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb7efbfb2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb7efc0bc in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0xb7efe88a in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#27 0xb6fe46e7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#28 0x08079839 in ?? ()
#29 0xb6b8a450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x0805d451 in _start ()
#0  0xb7f91410 in __kernel_vsyscall ()
Comment 1 Phil Rigby 2008-10-08 20:50:15 UTC
Confirmed, happened to me on 4.0.5 and the current 4.1.2.
Comment 2 Aaron J. Seigo 2010-06-04 22:07:34 UTC

*** This bug has been marked as a duplicate of bug 168427 ***