Bug 215013 - Dolphin crashes because of DBus
Summary: Dolphin crashes because of DBus
Status: RESOLVED DUPLICATE of bug 208921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-17 19:59 UTC by Frédéric COIFFIER
Modified: 2009-11-17 20:22 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 Frédéric COIFFIER 2009-11-17 19:59:50 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-gentoo-r1 i686

What I was doing when the application crashed:
Dolphin has crashed after opening a file

The problem seems to be due to DBus

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_connection_lock (connection=) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-connection.c:361
#7  0x486da106 in _dbus_pending_call_get_connection_and_lock (pending=) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-pending-call.c:307
#8  0x486c81e7 in reply_handler_timeout (data=) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-connection.c:3237
#9  0x486df430 in dbus_timeout_handle (timeout=) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-timeout.c:473
#10 0x489f016a in q_dbus_timeout_handle (this=<value optimized out>, e=) at ./qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (this=<value optimized out>, e=) at qdbusintegrator.cpp:1023
#12 0x4888d5f4 in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1066
#13 0x48e018fc in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:4065
#14 0x48e0322d in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3961
#15 0x49b84832 in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#16 0x48877ecd in QCoreApplication::notifyInternal (this=) at kernel/qcoreapplication.cpp:606
#17 0x488aa5f0 in QCoreApplication::sendEvent (this=<value optimized out>) at kernel/qcoreapplication.h:213
#18 QTimerInfoList::activateTimers (this=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:580
#19 0x488a770f in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165
#20 0x48452b9f in g_main_dispatch (context=0x9a1f290) at gmain.c:1960
#21 IA__g_main_context_dispatch (context=0x9a1f290) at gmain.c:2513
#22 0x484565b8 in g_main_context_iterate (context=0x9a1f290, block=<value optimized out>, dispatch=1, self=0x9a1d860) at gmain.c:2591
#23 0x484566df in IA__g_main_context_iteration (context=0x9a1f290, may_block=1) at gmain.c:2654
#24 0x488a7659 in QEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#25 0x48eb0a0b in QGuiEventDispatcherGlib::processEvents (this=) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x488767be in QEventLoop::processEvents (this=) at kernel/qeventloop.cpp:149
#27 0x48876ce2 in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:197
#28 0x4887b6a6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x48e017b5 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0x0807ba3b in main (argc=5, argv=0xbfa509d4) at /var/tmp/portage/kde-base/dolphin-4.3.3/work/dolphin-4.3.3/dolphin/src/main.cpp:94

This bug may be a duplicate of or related to bug 214771

Reported using DrKonqi
Comment 1 Jonathan Thomas 2009-11-17 20:22:16 UTC

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