Bug 237328

Summary: Dolphin Segfaults Unexpectedly
Product: [Applications] dolphin Reporter: Yasha B.-K. <yashabk>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Yasha B.-K. 2010-05-12 03:22:20 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32.11-99.fc12.i686 i686
Distribution: "Fedora release 12 (Constantine)"

-- Information about the crash:
Dolphin crashed while switching between an emacs window and an Okular window. The Dolphin window was open to the directory containing the file I was editing, but I was not doing anything in Dolphin at the time.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_pthread_mutex_lock (mutex=<value optimized out>) at dbus-sysdeps-pthread.c:137
#7  0x00d70249 in _dbus_mutex_lock (mutex=<value optimized out>) at dbus-threads.c:148
#8  0x00d575c6 in _dbus_connection_lock (connection=<value optimized out>) at dbus-connection.c:355
#9  0x00d6aec6 in _dbus_pending_call_get_connection_and_lock (pending=<value optimized out>) at dbus-pending-call.c:307
#10 0x00d5b986 in reply_handler_timeout (data=<value optimized out>) at dbus-connection.c:3156
#11 0x00d6fde3 in dbus_timeout_handle (timeout=<value optimized out>) at dbus-timeout.c:473
#12 0x00124f80 in q_dbus_timeout_handle (this=0x9c03dd8, e=0xbf835120) at qdbus_symbols_p.h:172
#13 QDBusConnectionPrivate::timerEvent (this=0x9c03dd8, e=0xbf835120) at qdbusintegrator.cpp:1035
#14 0x0475ca94 in QObject::event (this=0x9c03dd8, e=0xbf835120) at kernel/qobject.cpp:1212
#15 0x0213bd2c in QApplicationPrivate::notify_helper (this=0x9c0c3f8, receiver=0x9c03dd8, e=0xbf835120) at kernel/qapplication.cpp:4300
#16 0x02142556 in QApplication::notify (this=0xbf835484, receiver=0x9c03dd8, e=0xbf835120) at kernel/qapplication.cpp:3704
#17 0x02c027cb in KApplication::notify (this=0xbf835484, receiver=0x9c03dd8, event=0xbf835120) at /usr/src/debug/kdelibs-4.4.2/kdeui/kernel/kapplication.cpp:302
#18 0x0474cc03 in QCoreApplication::notifyInternal (this=0xbf835484, receiver=0x9c03dd8, event=0xbf835120) at kernel/qcoreapplication.cpp:704
#19 0x04777afe in sendEvent (this=0x9c13134) at kernel/qcoreapplication.h:215
#20 QTimerInfoList::activateTimers (this=0x9c13134) at kernel/qeventdispatcher_unix.cpp:603
#21 0x04775188 in timerSourceDispatch (source=0x9c13168) at kernel/qeventdispatcher_glib.cpp:184
#22 idleTimerSourceDispatch (source=0x9c13168) at kernel/qeventdispatcher_glib.cpp:231
#23 0x0090dfb8 in g_main_dispatch (context=0x9c12490) at gmain.c:1960
#24 IA__g_main_context_dispatch (context=0x9c12490) at gmain.c:2513
#25 0x009118e8 in g_main_context_iterate (context=0x8a3eb0, block=1, dispatch=1, self=0x9c0f0a8) at gmain.c:2591
#26 0x00911a14 in IA__g_main_context_iteration (context=0x9c12490, may_block=1) at gmain.c:2654
#27 0x04774e46 in QEventDispatcherGlib::processEvents (this=0x9bee340, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#28 0x021ea0e6 in QGuiEventDispatcherGlib::processEvents (this=0x9bee340, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x0474b2da in QEventLoop::processEvents (this=0xbf8353e4, flags=...) at kernel/qeventloop.cpp:149
#30 0x0474b61a in QEventLoop::exec (this=0xbf8353e4, flags=...) at kernel/qeventloop.cpp:201
#31 0x0474dce7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x0213bdd8 in QApplication::exec () at kernel/qapplication.cpp:3579
#33 0x08078487 in main (argc=3, argv=0xbf835664) at /usr/src/debug/kdebase-4.4.2/apps/dolphin/src/main.cpp:101

This bug may be a duplicate of or related to bug 208921.

Possible duplicates by query: bug 236951, bug 232669, bug 229551, bug 217407, bug 212280.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-05-12 14:52:54 UTC
Thanks for the bug report! This seems to be a duplicate of a bug in D-Bus.

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