Bug 178521 - dolphin crash in folder deletion
Summary: dolphin crash in folder deletion
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-23 00:08 UTC by manolis
Modified: 2008-12-23 12:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description manolis 2008-12-23 00:08:43 UTC
Version:           trunk (using Devel)
Compiler:          gcc 
OS:                Linux
Installed from:    Compiled sources

I cannot reproduce it
It concerned a folder created with ktorrent and had zero bytes received for a torrent
Upon deletion of the torrent inside ktorrent the app would crash with no crashhandler.
I tried then to delete it throught dolphin and then dolphin crashed (it deleted the folder though)

backtrace:
Application: Dolphin (dolphin), signal SIGABRT
0x00007fbcf2aa2d91 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7fbcf7020750 (LWP 26763)):
[KCrash Handler]
#5  0x00007fbcf2a351f5 in raise () from /lib/libc.so.6
#6  0x00007fbcf2a36713 in abort () from /lib/libc.so.6
#7  0x00007fbcf43332ed in qt_message_output () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007fbcf4333427 in qFatal () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007fbcf6bc3c80 in ?? () from /usr/kde/live/lib64/libkio.so.5
#10 0x00007fbcf6bc4c1b in ?? () from /usr/kde/live/lib64/libkio.so.5
#11 0x00007fbcf6bc55bc in ?? () from /usr/kde/live/lib64/libkio.so.5
#12 0x00007fbcf4472d54 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007fbcf6bd5112 in KDirWatch::dirty () from /usr/kde/live/lib64/libkio.so.5
#14 0x00007fbcf6bd53a5 in KDirWatch::setDirty () from /usr/kde/live/lib64/libkio.so.5
#15 0x00007fbcf6bd6669 in ?? () from /usr/kde/live/lib64/libkio.so.5
#16 0x00007fbcf6bd9438 in ?? () from /usr/kde/live/lib64/libkio.so.5
#17 0x00007fbcf6bda558 in ?? () from /usr/kde/live/lib64/libkio.so.5
#18 0x00007fbcf4472d54 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007fbcf446b7b3 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00007fbcf368749d in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4
#21 0x00007fbcf3688b1a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4
#22 0x00007fbcf52569a1 in KApplication::notify () from /usr/kde/live/lib64/libkdeui.so.5
#23 0x00007fbcf4459d6e in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007fbcf448a685 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007fbcf448c568 in QEventDispatcherUNIX::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007fbcf372c18a in ?? () from /usr/lib64/qt4/libQtGui.so.4
#27 0x00007fbcf44589b2 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#28 0x00007fbcf4458e4d in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4
#29 0x00007fbcf445e4af in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4
#30 0x000000000043ec7d in ?? ()
#31 0x00007fbcf2a215b6 in __libc_start_main () from /lib/libc.so.6
#32 0x00000000004224e9 in _start ()
Comment 1 Dario Andres 2008-12-23 01:10:58 UTC
What SVN revision are you using? This is related to bug 177125 that should be fixed in the revision 900309. Thanks :)
Comment 2 manolis 2008-12-23 01:30:51 UTC
r900391
last changed revision of kdebase r900379
Comment 3 David Faure 2008-12-23 10:54:17 UTC
And which revision of kdelibs? If it was < 900309 then this is definitely Bug 177125 (and I think it is).
Comment 4 manolis 2008-12-23 11:04:10 UTC
r900382 , last changed r900376

The sad thing is that I cannot reproduce it because it happened only in the specific folder.
You can "close" it if you want and I will open a new bug if it happens again (hopefully with a more full backtrace)
Comment 5 David Faure 2008-12-23 12:29:23 UTC
In addition, Dolphin is a kuniqueapplication (and is kdeinit-enabled) so if you upgrade kdelibs you have to close all dolphin windows before opening a new one _from a terminal_ otherwise your older kdelibs is still used ;)
OK, closing.