Application: dolphin (4.11.1) KDE Platform Version: 4.11.1 Qt Version: 4.8.5 Operating System: Linux 3.11.1-200.fc19.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I inserted an USB key formated with FAT32. At this moment Dolphin crashed. It was a one time error, not reproduced on subsequent USB key inserts. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7faaec1628c0 (LWP 2053))] Thread 2 (Thread 0x7faadea63700 (LWP 2057)): #0 0x0000003e73c86f9a in g_mutex_get_impl (mutex=0x7faad00009a0) at gthread-posix.c:121 #1 0x0000003e73c87249 in g_mutex_lock (mutex=mutex@entry=0x7faad00009a0) at gthread-posix.c:210 #2 0x0000003e73c477a9 in g_main_context_prepare (context=context@entry=0x7faad00009a0, priority=priority@entry=0x7faadea62ba8) at gmain.c:3330 #3 0x0000003e73c48013 in g_main_context_iterate (context=context@entry=0x7faad00009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3681 #4 0x0000003e73c481fc in g_main_context_iteration (context=0x7faad00009a0, may_block=1) at gmain.c:3762 #5 0x000000343b3a7166 in QEventDispatcherGlib::processEvents (this=0x7faad00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x000000343b378ecf in QEventLoop::processEvents (this=this@entry=0x7faadea62ce0, flags=...) at kernel/qeventloop.cpp:149 #7 0x000000343b3791c5 in QEventLoop::exec (this=this@entry=0x7faadea62ce0, flags=...) at kernel/qeventloop.cpp:204 #8 0x000000343b27866f in QThread::exec (this=this@entry=0xcd4a20) at thread/qthread.cpp:536 #9 0x000000343b35a733 in QInotifyFileSystemWatcherEngine::run (this=0xcd4a20) at io/qfilesystemwatcher_inotify.cpp:256 #10 0x000000343b27ad0f in QThreadPrivate::start (arg=0xcd4a20) at thread/qthread_unix.cpp:338 #11 0x0000003e70c07c53 in start_thread (arg=0x7faadea63700) at pthread_create.c:308 #12 0x0000003e704f5d3d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7faaec1628c0 (LWP 2053)): [KCrash Handler] #6 0x000000343c0177c7 in QDomNode::toElement (this=this@entry=0x7fff817bdbe0) at dom/qdom.cpp:7281 #7 0x0000003fd03b8b8b in KBookmarkGroup::findToolbar (this=this@entry=0x7fff817bdd10) at /usr/src/debug/kdelibs-4.11.1/kio/bookmarks/kbookmark.cc:253 #8 0x0000003fd03bfd21 in KBookmarkManager::saveAs (this=this@entry=0xc9d4d0, filename=..., toolbarCache=toolbarCache@entry=true) at /usr/src/debug/kdelibs-4.11.1/kio/bookmarks/kbookmarkmanager.cc:415 #9 0x0000003fd03bfea1 in KBookmarkManager::save (this=this@entry=0xc9d4d0, toolbarCache=toolbarCache@entry=true) at /usr/src/debug/kdelibs-4.11.1/kio/bookmarks/kbookmarkmanager.cc:398 #10 0x0000003fd03c2b38 in KBookmarkManager::emitChanged (this=0xc9d4d0, group=...) at /usr/src/debug/kdelibs-4.11.1/kio/bookmarks/kbookmarkmanager.cc:553 #11 0x0000003fd905d1d1 in PlacesItemModel::saveBookmarks() () from /lib64/libkdeinit4_dolphin.so #12 0x0000003fd9062d7d in PlacesItemModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.57] () from /lib64/libkdeinit4_dolphin.so #13 0x000000343b38df78 in QMetaObject::activate (sender=0xf7b7c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #14 0x000000343b392141 in QObject::event (this=0xf7b7c0, e=<optimized out>) at kernel/qobject.cpp:1156 #15 0x00000031ddfc84dc in QApplicationPrivate::notify_helper (this=this@entry=0xa5b900, receiver=receiver@entry=0xf7b7c0, e=e@entry=0x7fff817be2a0) at kernel/qapplication.cpp:4562 #16 0x00000031ddfceaa0 in QApplication::notify (this=this@entry=0x7fff817be650, receiver=receiver@entry=0xf7b7c0, e=e@entry=0x7fff817be2a0) at kernel/qapplication.cpp:4348 #17 0x0000003fcf43fd2a in KApplication::notify (this=0x7fff817be650, receiver=0xf7b7c0, event=0x7fff817be2a0) at /usr/src/debug/kdelibs-4.11.1/kdeui/kernel/kapplication.cpp:311 #18 0x000000343b37a26d in QCoreApplication::notifyInternal (this=0x7fff817be650, receiver=0xf7b7c0, event=0x7fff817be2a0) at kernel/qcoreapplication.cpp:949 #19 0x000000343b3a9c13 in sendEvent (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #20 QTimerInfoList::activateTimers (this=0xa59cb0) at kernel/qeventdispatcher_unix.cpp:621 #21 0x000000343b3a6f11 in timerSourceDispatch (source=source@entry=0xa59c50) at kernel/qeventdispatcher_glib.cpp:186 #22 0x0000003e73c47e06 in g_main_dispatch (context=0xa5c720) at gmain.c:3054 #23 g_main_context_dispatch (context=context@entry=0xa5c720) at gmain.c:3630 #24 0x0000003e73c48158 in g_main_context_iterate (context=context@entry=0xa5c720, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701 #25 0x0000003e73c481fc in g_main_context_iteration (context=0xa5c720, may_block=1) at gmain.c:3762 #26 0x000000343b3a7145 in QEventDispatcherGlib::processEvents (this=0xa255d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #27 0x00000031de064fc6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #28 0x000000343b378ecf in QEventLoop::processEvents (this=this@entry=0x7fff817be520, flags=...) at kernel/qeventloop.cpp:149 #29 0x000000343b3791c5 in QEventLoop::exec (this=this@entry=0x7fff817be520, flags=...) at kernel/qeventloop.cpp:204 #30 0x000000343b37e45b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #31 0x0000003fd9051427 in kdemain () from /lib64/libkdeinit4_dolphin.so #32 0x0000003e70421b75 in __libc_start_main (main=0x4008a0 <main>, argc=5, ubp_av=0x7fff817be788, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff817be778) at libc-start.c:258 #33 0x00000000004008d1 in _start () The reporter indicates this bug may be a duplicate of or related to bug 320006. Possible duplicates by query: bug 324726, bug 322275, bug 320006. Reported using DrKonqi
Thanks for the bug report! (In reply to comment #0) > It was a one time error, not reproduced on subsequent USB key inserts. In such cases, it's not really necessary to open a new bug report if you've already found a duplicate and you cannot provide any additional information that might help to track down the problem. If in doubt, you can always add a comment to the existing report. *** This bug has been marked as a duplicate of bug 320006 ***