Bug 243033

Summary: Dolphin Crashes in D-Bus
Product: [Applications] dolphin Reporter: Jon Skanes <jon>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jon Skanes 2010-06-28 15:12:39 UTC
Application: dolphin (1.5)
KDE Platform Version: 4.4.90 (KDE 4.4.90 (KDE 4.5 RC1))
Qt Version: 4.7.0
Operating System: Linux 2.6.32-22-generic-pae i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
Dolphin was oppened to an ntfs-3g partation from which I opened a video file in Dragon.  I switched to another desktop while watching the video and Dolphin crashed.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4c1e710 (LWP 4283))]

Thread 2 (Thread 0xac757b70 (LWP 4317)):
#0  0xb7730430 in __kernel_vsyscall ()
#1  0xb5517342 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0xb7611a34 in __pthread_cond_timedwait (cond=0x8d0f2b8, mutex=0x8d0f2a0, abstime=0xac757320) at forward.c:152
#3  0xb1b33ce7 in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xb4c1e710 (LWP 4283)):
[KCrash Handler]
#7  _dbus_connection_lock (connection=0x6c69666b) at dbus-connection.c:355
#8  0xb4dd0695 in _dbus_pending_call_get_connection_and_lock (pending=0x91098d8) at dbus-pending-call.c:307
#9  0xb4dc1505 in reply_handler_timeout (data=0x91098d8) at dbus-connection.c:3156
#10 0xb4dd5492 in dbus_timeout_handle (timeout=0x8ffa070) at dbus-timeout.c:473
#11 0xb5cd9635 in q_dbus_timeout_handle (this=0x86bb7a8, e=0xbf81dbe0) at qdbus_symbols_p.h:174
#12 QDBusConnectionPrivate::timerEvent (this=0x86bb7a8, e=0xbf81dbe0) at qdbusintegrator.cpp:1040
#13 0xb5ba2014 in QObject::event (this=0x86bb7a8, e=0x91098d8) at kernel/qobject.cpp:1183
#14 0xb610932c in QApplicationPrivate::notify_helper (this=0x86cbd78, receiver=0x86bb7a8, e=0xbf81dbe0) at kernel/qapplication.cpp:4358
#15 0xb61106fe in QApplication::notify (this=0xbf81df50, receiver=0x86bb7a8, e=0xbf81dbe0) at kernel/qapplication.cpp:3762
#16 0xb6c6f0da in KApplication::notify (this=0xbf81df50, receiver=0x86bb7a8, event=0xbf81dbe0) at ../../kdeui/kernel/kapplication.cpp:309
#17 0xb5b8f6cb in QCoreApplication::notifyInternal (this=0xbf81df50, receiver=0x86bb7a8, event=0xbf81dbe0) at kernel/qcoreapplication.cpp:732
#18 0xb5bc1426 in QCoreApplication::sendEvent (this=0x86c7234) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x86c7234) at kernel/qeventdispatcher_unix.cpp:602
#20 0xb5bbe227 in timerSourceDispatch (source=0x86c7270) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=0x86c7270) at kernel/qeventdispatcher_glib.cpp:231
#22 0xb521f5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0xb52232d8 in ?? () from /lib/libglib-2.0.so.0
#24 0xb52234b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0xb5bbdee5 in QEventDispatcherGlib::processEvents (this=0x86c2ff8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#26 0xb61ca105 in QGuiEventDispatcherGlib::processEvents (this=0x86c2ff8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0xb5b8e1a9 in QEventLoop::processEvents (this=0xbf81dea4, flags=) at kernel/qeventloop.cpp:149
#28 0xb5b8e5fa in QEventLoop::exec (this=0xbf81dea4, flags=...) at kernel/qeventloop.cpp:201
#29 0xb5b92baf in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#30 0xb6108157 in QApplication::exec () at kernel/qapplication.cpp:3637
#31 0xb76e020b in kdemain (argc=5, argv=0xbf81e144) at ../../../../apps/dolphin/src/main.cpp:98
#32 0x080485fb in main (argc=5, argv=0xbf81e144) at dolphin_dummy.cpp:3

Possible duplicates by query: bug 242725, bug 242574, bug 241480, bug 240458, bug 238659.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-06-30 15:20:28 UTC
Thanks for the bug report! This crash is known already - it's due to a bug in
the D-Bus library.

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