Bug 217415 - Dolphin crashed (dbus related) [_dbus_connection_lock, _dbus_pending_call_get_connection_and_lock, reply_handler_timeout]
Summary: Dolphin crashed (dbus related) [_dbus_connection_lock, _dbus_pending_call_get...
Status: RESOLVED DUPLICATE of bug 208921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-05 10:30 UTC by Unknown
Modified: 2009-12-05 11:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2009-12-05 10:30:20 UTC
Application: dolphin (1.3.80)
KDE Platform Version: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1)) (Compiled from sources)
Qt Version: 4.6.0
Operating System: Linux 2.6.32 i686
Distribution: "Gentoo Base System release 2.0.1"

-- Information about the crash:
Dolphin keeps crashing when browsing pictures from pendrive or phone card. Don't know if it is realated to that or to ssh network directory connection… But when doing those things it keeps crashing (same was with 4.3.77 and 4.3.75). (-; Will try to reproduce this with only one of mentioned activities at a time.

The crash can be reproduced some of the times.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb5743846 in _dbus_connection_lock (connection=0x68537369) at dbus-connection.c:355
#7  0xb5762ccb in _dbus_pending_call_get_connection_and_lock (pending=0xa0f0638) at dbus-pending-call.c:309
#8  0xb574d426 in reply_handler_timeout (data=0xa0f0638) at dbus-connection.c:3116
#9  0xb5769e12 in dbus_timeout_handle (timeout=0xa0f0118) at dbus-timeout.c:473
#10 0xb6b23fd0 in QDBusConnectionPrivate::timerEvent (this=0x9f407a0, e=0xbfb5e33c) at ./qdbus_symbols_p.h:172
#11 0xb69fa30c in QObject::event (this=0x9f407a0, e=0xbfb5e33c) at kernel/qobject.cpp:1216
#12 0xb5ebb66f in QApplicationPrivate::notify_helper (this=0x9f49038, receiver=0x9f407a0, e=0xbfb5e33c) at kernel/qapplication.cpp:4242
#13 0xb5ec3534 in QApplication::notify (this=0xbfb5e5cc, receiver=0x9f407a0, e=0xbfb5e33c) at kernel/qapplication.cpp:4207
#14 0xb6fcbc04 in KApplication::notify (this=0xbfb5e5cc, receiver=0x9f407a0, event=0xbfb5e33c) at /home/porttmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdeui/kernel/kapplication.cpp:302
#15 0xb69e7d02 in QCoreApplication::notifyInternal (this=0xbfb5e5cc, receiver=0x9f407a0, event=0xbfb5e33c) at kernel/qcoreapplication.cpp:704
#16 0xb6a1bc8e in QTimerInfoList::activateTimers (this=0x9f50134) at kernel/qcoreapplication.h:215
#17 0xb6a17f58 in idleTimerSourceDispatch (source=0x9f50170) at kernel/qeventdispatcher_glib.cpp:184
#18 0xb56844fb in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x09f4f69c in ?? ()
#20 0x09f50170 in ?? ()
#21 0xb57223b8 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb57223e0 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb6a17f30 in timerSourceDispatch (source=0x748dc35d) at kernel/qeventdispatcher_glib.cpp:186
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

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

Possible duplicates by query: bug 217407, bug 217078, bug 216959, bug 216026, bug 216008.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-12-05 11:50:00 UTC
Thanks for the bug report! A crash of this kind (crash in DBus code, apparently
related to Nepomuk) has been reported quite a few times already.

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