Application: dolphin (4.11.1) KDE Platform Version: 4.11.1 Qt Version: 4.8.2 Operating System: Linux 3.2.0-53-generic-pae i686 Distribution: Ubuntu 12.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Plugged in usb drive. Clicked on drive letter in dolphin then it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xafb9f740 (LWP 7695))] Thread 3 (Thread 0xac710b40 (LWP 7715)): #0 0xb75d1f83 in ?? () from /lib/i386-linux-gnu/libc.so.6 #1 0xb75a38d8 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #2 0xb4aaa3f0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4a6b04c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb4a6b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb5815de7 in QEventDispatcherGlib::processEvents (this=0xabe00488, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb57e16ad in QEventLoop::processEvents (this=0xac710190, flags=...) at kernel/qeventloop.cpp:149 #7 0xb57e1949 in QEventLoop::exec (this=0xac710190, flags=...) at kernel/qeventloop.cpp:204 #8 0xb56caa1c in QThread::exec (this=0x9dbbf90) at thread/qthread.cpp:501 #9 0xb57becfd in QInotifyFileSystemWatcherEngine::run (this=0x9dbbf90) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb56cdeb0 in QThreadPrivate::start (arg=0x9dbbf90) at thread/qthread_unix.cpp:307 #11 0xb1c87101 in ?? () from /usr/lib/libGL.so.1 #12 0x5c8b0824 in ?? () #13 0xbab80424 in ?? () #14 0x65000000 in ?? () #15 0x001015ff in ?? () #16 0xd3890000 in ?? () #17 0xfff0013d in ?? () #18 0xc30173ff in ?? () #19 0x0fc442e8 in ?? () #20 0xafc18100 in ?? () from /usr/lib/i386-linux-gnu/libvorbisenc.so.2 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 2 (Thread 0xabc75b40 (LWP 7720)): #0 0xb4b3ee13 in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0 #1 0xb75a3904 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #2 0xb4aaa3f0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4a6a83c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb4a6af6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb4a6b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb5815de7 in QEventDispatcherGlib::processEvents (this=0xab300488, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0xb57e16ad in QEventLoop::processEvents (this=0xabc75190, flags=...) at kernel/qeventloop.cpp:149 #8 0xb57e1949 in QEventLoop::exec (this=0xabc75190, flags=...) at kernel/qeventloop.cpp:204 #9 0xb56caa1c in QThread::exec (this=0x9cf1ae8) at thread/qthread.cpp:501 #10 0xb57becfd in QInotifyFileSystemWatcherEngine::run (this=0x9cf1ae8) at io/qfilesystemwatcher_inotify.cpp:248 #11 0xb56cdeb0 in QThreadPrivate::start (arg=0x9cf1ae8) at thread/qthread_unix.cpp:307 #12 0xb1c87101 in ?? () from /usr/lib/libGL.so.1 #13 0x5c8b0824 in ?? () #14 0xbab80424 in ?? () #15 0x65000000 in ?? () #16 0x001015ff in ?? () #17 0xd3890000 in ?? () #18 0xfff0013d in ?? () #19 0xc30173ff in ?? () #20 0x0fc442e8 in ?? () #21 0xafc18100 in ?? () from /usr/lib/i386-linux-gnu/libvorbisenc.so.2 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 1 (Thread 0xafb9f740 (LWP 7695)): [KCrash Handler] #7 0xb6b45c2d in QDomNode::toElement (this=0xbfd6de24) at dom/qdom.cpp:7281 #8 0xb6d18357 in KBookmarkGroup::findToolbar (this=0xbfd6df04) at ../../kio/bookmarks/kbookmark.cc:253 #9 0xb6d205be in KBookmarkManager::saveAs (this=0x9ceb5f0, filename=..., toolbarCache=true) at ../../kio/bookmarks/kbookmarkmanager.cc:415 #10 0xb6d207ae in KBookmarkManager::save (this=0x9ceb5f0, toolbarCache=true) at ../../kio/bookmarks/kbookmarkmanager.cc:398 #11 0xb6d207f2 in KBookmarkManager::emitChanged (this=0x9ceb5f0, group=...) at ../../kio/bookmarks/kbookmarkmanager.cc:553 #12 0xb76c24e3 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so #13 0xb57f9bb1 in QMetaObject::activate (sender=0xa0d0820, m=0xb59414d8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3547 #14 0xb584cb25 in QTimer::timeout (this=0xa0d0820) at .moc/release-shared/moc_qtimer.cpp:148 #15 0xb5802a66 in QTimer::timerEvent (this=0xa0d0820, e=0xbfd6e58c) at kernel/qtimer.cpp:280 #16 0xb57fdfc4 in QObject::event (this=0xa0d0820, e=0xbfd6e58c) at kernel/qobject.cpp:1157 #17 0xb5d54df4 in notify_helper (e=0xbfd6e58c, receiver=0xa0d0820, this=0x9b770f0) at kernel/qapplication.cpp:4556 #18 QApplicationPrivate::notify_helper (this=0x9b770f0, receiver=0xa0d0820, e=0xbfd6e58c) at kernel/qapplication.cpp:4528 #19 0xb5d5a15d in QApplication::notify (this=0xbfd6e58c, receiver=0xa0d0820, e=0xbfd6e58c) at kernel/qapplication.cpp:4285 #20 0xb68dad71 in KApplication::notify (this=0xbfd6e8a8, receiver=0xa0d0820, event=0xbfd6e58c) at ../../kdeui/kernel/kapplication.cpp:311 #21 0xb57e2e0e in QCoreApplication::notifyInternal (this=0xbfd6e8a8, receiver=0xa0d0820, event=0xbfd6e58c) at kernel/qcoreapplication.cpp:915 #22 0xb5817e90 in sendEvent (event=0xbfd6e58c, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #23 QTimerInfoList::activateTimers (this=0x9b7b7b4) at kernel/qeventdispatcher_unix.cpp:611 #24 0xb58155f8 in timerSourceDispatch (source=0x9b7b780) at kernel/qeventdispatcher_glib.cpp:186 #25 timerSourceDispatch (source=0x9b7b780) at kernel/qeventdispatcher_glib.cpp:180 #26 0xb5815632 in idleTimerSourceDispatch (source=0x9b786c0) at kernel/qeventdispatcher_glib.cpp:233 #27 0xb4a6ad46 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #28 0xb4a6b0e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #29 0xb4a6b1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #30 0xb5815d87 in QEventDispatcherGlib::processEvents (this=0x9b51dd0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #31 0xb5e0da1a in QGuiEventDispatcherGlib::processEvents (this=0x9b51dd0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #32 0xb57e16ad in QEventLoop::processEvents (this=0xbfd6e814, flags=...) at kernel/qeventloop.cpp:149 #33 0xb57e1949 in QEventLoop::exec (this=0xbfd6e814, flags=...) at kernel/qeventloop.cpp:204 #34 0xb57e734a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #35 0xb5d529c4 in QApplication::exec () at kernel/qapplication.cpp:3817 #36 0xb76b3357 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so #37 0x0804850b in ?? () #38 0xb74c04d3 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 #39 0x08048531 in _start () Possible duplicates by query: bug 322275, bug 320006. Reported using DrKonqi
Thanks for the bug report. Looks similar to bug 320006. Could you try to obtain a Valgrind log and attach it here? See http://community.kde.org/Dolphin/FAQ/Crashes for details. Thanks.
I do not have valgrind installed. ________________________________ From: Frank Reininghaus <frank78ac@googlemail.com> To: eddieg80@yahoo.com Sent: Tuesday, September 10, 2013 4:10 AM Subject: [dolphin] [Bug 324726] usb drive crash in dolphin https://bugs.kde.org/show_bug.cgi?id=324726 --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> --- Thanks for the bug report. Looks similar to bug 320006. Could you try to obtain a Valgrind log and attach it here? See http://community.kde.org/Dolphin/FAQ/Crashes for details. Thanks.
(In reply to comment #2) > I do not have valgrind installed. In that case, there are two options: (a) You install Valgrind and try to obtain a log of the crash. If you can reproduce the crash inside Valgrind, there is a chance that it will provide valuable information which may help to fix the crash. (b) You do not install Valgrind. In that case, it's unlikely that the cause of the crash (which is probably inside kdelibs) will be found in the near future. I also kindly ask you to not report any Dolphin bugs in the future then. You are still very welcome to use Dolphin, of course, but please note that the bug tracker is full of reports with incomplete information, and adding more of these just wastes everyone's time (including your own). Thanks for your understanding. *** This bug has been marked as a duplicate of bug 320006 ***
Created attachment 82488 [details] New crash information added by DrKonqi dolphin (4.11.1) on KDE Platform 4.11.1 using Qt 4.8.4 - What I was doing when the application crashed: Hooked up a 32 GB USB key to the usb port, clicked on automounted device. -- Backtrace (Reduced): #7 0xb6bb39fd in QDomNode::toElement (this=this@entry=0xbfec8748) at dom/qdom.cpp:7281 #8 0xb6d725db in KBookmarkGroup::findToolbar (this=this@entry=0xbfec87d4) at ../../kio/bookmarks/kbookmark.cc:253 #9 0xb6d7ce5e in KBookmarkManager::saveAs (this=this@entry=0x8bb9b68, filename=..., toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:415 #10 0xb6d7d04e in KBookmarkManager::save (this=this@entry=0x8bb9b68, toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:398 #11 0xb6d7d092 in KBookmarkManager::emitChanged (this=0x8bb9b68, group=...) at ../../kio/bookmarks/kbookmarkmanager.cc:553