Bug 258373 - dophin crash at startup
Summary: dophin crash at startup
Status: RESOLVED DUPLICATE of bug 226725
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: 2010-11-30 13:51 UTC by Suhan Andrei
Modified: 2010-11-30 14:12 UTC (History)
0 users

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 Suhan Andrei 2010-11-30 13:51:17 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.27.41-170.2.117.fc10.x86_64 x86_64
Distribution: "Fedora release 10 (Cambridge)"

What I was doing when the application crashed:
restarted PC

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  QMutex::lock (this=0x100000009) at thread/qmutex.cpp:152
#6  0x0000003e3ee41b69 in mutex_lock (mutex=0x100000009) at qdbusthread.cpp:69
#7  0x000000302020b5cd in _dbus_connection_lock (connection=0x2b7abf0) at dbus-connection.c:355
#8  0x000000302021cb7d in _dbus_pending_call_get_connection_and_lock (pending=0x2b50800) at dbus-pending-call.c:309
#9  0x000000302020fc5f in reply_handler_timeout (data=0x100000009) at dbus-connection.c:3116
#10 0x0000003e3ee19896 in q_dbus_timeout_handle () at ./qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (this=0x2656990, e=0x7fff339ea430) at qdbusintegrator.cpp:1023
#12 0x0000003e3c353473 in QObject::event (this=0x2656990, e=0x19) at kernel/qobject.cpp:1074
#13 0x00000032fd39001d in QApplicationPrivate::notify_helper (this=0x2668600, receiver=0x2656990, e=0x7fff339ea430) at kernel/qapplication.cpp:4065
#14 0x00000032fd39825a in QApplication::notify (this=0x7fff339ea770, receiver=0x2656990, e=0x7fff339ea430) at kernel/qapplication.cpp:4030
#15 0x00000032fea1351b in KApplication::notify (this=0x7fff339ea770, receiver=0x2656990, event=0x7fff339ea430) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#16 0x0000003e3c34378c in QCoreApplication::notifyInternal (this=0x7fff339ea770, receiver=0x2656990, event=0x7fff339ea430) at kernel/qcoreapplication.cpp:610
#17 0x0000003e3c370859 in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#18 QTimerInfoList::activateTimers (this=0x2665730) at kernel/qeventdispatcher_unix.cpp:580
#19 0x0000003e3c36cd5d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#20 0x00000035bb8377bb in g_main_dispatch () at gmain.c:2144
#21 IA__g_main_context_dispatch (context=0x2664920) at gmain.c:2697
#22 0x00000035bb83af8d in g_main_context_iterate (context=0x2664920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778
#23 0x00000035bb83b14b in IA__g_main_context_iteration (context=0x2664920, may_block=1) at gmain.c:2841
#24 0x0000003e3c36ccbf in QEventDispatcherGlib::processEvents (this=0x263cd50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#25 0x00000032fd42753f in QGuiEventDispatcherGlib::processEvents (this=0x100000009, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x0000003e3c342022 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x0000003e3c3423f4 in QEventLoop::exec (this=0x7fff339ea6e0, flags=) at kernel/qeventloop.cpp:201
#28 0x0000003e3c3446c4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x00000000004372ad in main (argc=3, argv=0x7fff339eac58) at /usr/src/debug/kdebase-4.3.3/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Peter Penz 2010-11-30 14:12:38 UTC
hanks for the bug report! This is an issue in the D-Bus library which
has been reported already. It is fixed in D-Bus 1.3.1 and later:

http://bugreports.qt.nokia.com/browse/QTBUG-7475
https://bugs.freedesktop.org/show_bug.cgi?id=17754

If you cannot update to D-Bus 1.3.1 or later, you can disable tool tips and the
Information Panel as a workaround.

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