Bug 250827

Summary: Dolphin crashes while doing nothing
Product: [Applications] dolphin Reporter: Carlos F. Lange <carlos.lange>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Carlos F. Lange 2010-09-10 22:29:34 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.4-0.1-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
Dolphin was idle  for at least 5 minutes, while I was using Kontact, when it crashed.

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

Thread 2 (Thread 0x7f4c72847710 (LWP 3537)):
#0  0x00007f4c7e15f709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f4c71baf951 in metronom_sync_loop () from /usr/lib64/libxine.so.1
#2  0x00007f4c7e15aa4f in start_thread () from /lib64/libpthread.so.0
#3  0x00007f4c80fd682d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4c85225760 (LWP 3511)):
[KCrash Handler]
#5  _dbus_connection_lock (connection=0x6664702e4c41) at dbus-connection.c:355
#6  0x00007f4c7ce69b1d in _dbus_pending_call_get_connection_and_lock (pending=0x7f4c5c00cde0) at dbus-pending-call.c:307
#7  0x00007f4c7ce5bfce in reply_handler_timeout (data=0x7f4c5c00cde0) at dbus-connection.c:3163
#8  0x00007f4c82674cef in q_dbus_timeout_handle (this=0x6af130, e=0x7fff33273970) at qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (this=0x6af130, e=0x7fff33273970) at qdbusintegrator.cpp:1035
#10 0x00007f4c8235022e in QObject::event (this=0x6af130, e=0x7fff33273970) at kernel/qobject.cpp:1212
#11 0x00007f4c817304d4 in QApplicationPrivate::notify_helper (this=0x6bb7a0, receiver=0x6af130, e=0x7fff33273970) at kernel/qapplication.cpp:4302
#12 0x00007f4c81738aca in QApplication::notify (this=<value optimized out>, receiver=0x6af130, e=0x7fff33273970) at kernel/qapplication.cpp:4185
#13 0x00007f4c82e97c06 in KApplication::notify (this=0x7fff33273db0, receiver=0x6af130, event=0x7fff33273970) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#14 0x00007f4c8233ee4c in QCoreApplication::notifyInternal (this=0x7fff33273db0, receiver=0x6af130, event=0x7fff33273970) at kernel/qcoreapplication.cpp:726
#15 0x00007f4c8236a0c9 in sendEvent (this=0x6c4320) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x6c4320) at kernel/qeventdispatcher_unix.cpp:618
#17 0x00007f4c82366ff8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007f4c7c596a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f4c7c597270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f4c7c597510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f4c8236767f in QEventDispatcherGlib::processEvents (this=0x6968a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#23 0x00007f4c817d114e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f4c8233e292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f4c8233e495 in QEventLoop::exec (this=0x7fff33273d00, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f4c8234288b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#27 0x0000000000436c3d in _start ()

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

Possible duplicates by query: bug 250295, bug 250165, bug 249678, bug 249556, bug 249482.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-09-11 23:18:28 UTC
Thanks for the bug report! This looks like an issue in the D-Bus library which
has been reported already.

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