Bug 180352 - Dolphin Version 1.1.80 - Using KDE 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)) - Deleting/creating folders crashes Dolphin
Summary: Dolphin Version 1.1.80 - Using KDE 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)) - Dele...
Status: RESOLVED DUPLICATE of bug 177125
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-11 18:17 UTC by mathesis
Modified: 2009-01-11 19:14 UTC (History)
1 user (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 mathesis 2009-01-11 18:17:13 UTC
Version:            (using Devel)
Installed from:    Compiled sources

OS
I'm a Kubuntu 8.10 user. My system is updated according to the following depositories:
- deb http://ppa.launchpad.net/project-neon/ubuntu intrepid main
- deb-src http://ppa.launchpad.net/project-neon/ubuntu intrepid main
- deb http://ppa.launchpad.net/kubuntu-experimental/ubuntu intrepid main 





TROUBLE
Very difficult to describe since in many ways it can happen. The here below backtrace has been produced by:
- Creating a folder;
- Creating a new file in this folder;
- Moving the file out of the folder;
- Deleting the folder (at this stage I was disappointed, I was expecting Dolphin to crash because it is a way to reproduce the bug, but it didn't);
- Creating a folder --> then crash.

Note:
- Everything has been done in the same main folder;
- All discs are local ones;
- Most of the time, it is by deleting a folder just after having moved the files it contained that it crashes.

I encounter this bug since yesterday only, as I'm cleaning my mp3's I do a lot of renaming, moving of files/folders (quickly, I don't let my OS to breathe). I also do these operations while the mp3 is played by amarok. It shouldn't be a problem as it worked perfectly before with KDE 3.5.





BACKTRACES

Bla bla: signal 11 (SIGSEGV)
Cette pile des appels apparaît être inutilisable.
C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5e456c0 (LWP 7319)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb800b430 in __kernel_vsyscall ()
[Current thread is 0 (process 7319)]

Thread 1 (Thread 0xb5e456c0 (LWP 7319)):
#0  0xb800b430 in __kernel_vsyscall ()
#1  0xb647fdc0 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb647fbfe in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb78256f2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb78260f4 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb7e4fed1 in ?? () from /usr/lib/libkio.so.5
#7  0xb7e50133 in ?? () from /usr/lib/libkio.so.5
#8  0xb7e54791 in KDirModel::indexForUrl () from /usr/lib/libkio.so.5
#9  0xb7c7354c in DolphinView::restoreCurrentItem () from /usr/lib/libdolphinprivate.so.4
#10 0xb7c774f3 in DolphinView::qt_metacall () from /usr/lib/libdolphinprivate.so.4
#11 0xb6924a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb69257e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb7e38e27 in KDirLister::completed () from /usr/lib/libkio.so.5
#14 0xb7e4a23f in ?? () from /usr/lib/libkio.so.5
#15 0xb7e4b504 in ?? () from /usr/lib/libkio.so.5
#16 0xb6924a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb69257e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb743e413 in KJob::result () from /usr/lib/libkdecore.so.5
#19 0xb743e929 in KJob::emitResult () from /usr/lib/libkdecore.so.5
#20 0xb7e18475 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.5
#21 0xb7e185be in KIO::ListJob::slotFinished () from /usr/lib/libkio.so.5
#22 0xb7e1a3a3 in KIO::ListJob::qt_metacall () from /usr/lib/libkio.so.5
#23 0xb6924a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb69257e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb7ee2ce7 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.5
#26 0xb7ee6ab7 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#27 0xb7ee31c7 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#28 0xb7ed45bd in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#29 0xb7ed5733 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#30 0xb6924a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#31 0xb69257e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#32 0xb7ddedc7 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#33 0xb7de0e99 in ?? () from /usr/lib/libkio.so.5
#34 0xb7de1026 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#35 0xb691dbfb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#36 0xb691f771 in QObject::event () from /usr/lib/libQtCore.so.4
#37 0xb6b328ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#38 0xb6b3a72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#39 0xb77b0d3d in KApplication::notify () from /usr/lib/libkdeui.so.5
#40 0xb690fe61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#41 0xb6910ae5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#42 0xb6910cdd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#43 0xb693a82f in ?? () from /usr/lib/libQtCore.so.4
#44 0xb614d6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#45 0xb6150da3 in ?? () from /usr/lib/libglib-2.0.so.0
#46 0xb6150f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#47 0xb693a478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#48 0xb6bccea5 in ?? () from /usr/lib/libQtGui.so.4
#49 0xb690e52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#50 0xb690e6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#51 0xb6910da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#52 0xb6b32767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#53 0x08086a3f in _start ()
#0  0xb800b430 in __kernel_vsyscall ()





I'm really sorry if this is a duplicate, but you can be sure I searched for previous bugs, we are always sure our bug is different from what we read.
Comment 1 Dario Andres 2009-01-11 19:14:03 UTC
The root issue was fixed after 4.2Beta2 :)


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