Version: (using KDE 4.0.1) Installed from: Ubuntu Packages Dolphin crashed when I've pressed "Eject Disk" to eject a CD. I could not reproduce it and it looks like a problem in Solid, but I don't know. Backtrace: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb63c0720 (LWP 18607)] [New Thread 0xb4a8ab90 (LWP 18608)] [KCrash handler] #6 0xb67418b7 in Solid::StorageAccess::d_func (this=0x0) at /build/buildd/kde4libs-4.0.1/solid/solid/storageaccess.h:45 #7 0xb7755bcb in KFilePlacesModel::requestTeardown (this=0x81fb718, index=@0xbfa220dc) at /build/buildd/kde4libs-4.0.1/kfile/kfileplacesmodel.cpp:688 #8 0xb775a4ec in KFilePlacesSelector::activatePlace (this=0x81e5280, action=0x821afe8) at /build/buildd/kde4libs-4.0.1/kfile/kfileplacesselector.cpp:209 #9 0xb775aaf9 in KFilePlacesSelector::qt_metacall (this=0x81e5280, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfa2263c) at /build/buildd/kde4libs-4.0.1/obj-i486-linux-gnu/kfile/kfileplacesselector_p.moc:74 #10 0xb7f29cf4 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7f2a8c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb737c1c3 in QMenu::triggered () from /usr/lib/libQtGui.so.4 #13 0xb737d3bb in ?? () from /usr/lib/libQtGui.so.4 #14 0x081e51e8 in ?? () #15 0x0821afe8 in ?? () #16 0xffffff40 in ?? () #17 0xb75de990 in ?? () from /usr/lib/libQtGui.so.4 #18 0x00000000 in ?? () #0 0xb7fb8410 in __kernel_vsyscall ()
I cannot reproduce on revision 781559.
I cannot reproduce this issue on trunk... I've added Kevin (= Solid maintainer) to CC, maybe he has a hint.
May bug 163571 be related/duplicate of this ?
Have anyone experienced this bug again with a recent KDE version? (4.1.3 / 4.2beta2 / 4.2svn) ? Thanks :)
I'm not able to reproduce it too. Anyway it seems quite different from bug #163571.
Bug 178391 seems to be related/duplicate of this (using devel version). May this be re-opened ?
I'll suggest to keep this closed and leave bug #178391 opened: it has a better explanation and a better backtrace.