Bug 212667 - Dolphin Crashed for No Apparant Reason
Summary: Dolphin Crashed for No Apparant Reason
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-01 21:57 UTC by Stirling Westrup
Modified: 2009-11-01 22:28 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 Stirling Westrup 2009-11-01 21:57:42 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
I was navigating around my home directory, something I've done many times, but this time Dolphin crashed. No idea why. Is there some way to get better debugging on libdbus? So far all my dolphin crashes seem to have involved that library, but there's no debug version in the package archives.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f64def80244 in ?? () from /lib/libdbus-1.so.3
#6  0x00007f64def91bcd in ?? () from /lib/libdbus-1.so.3
#7  0x00007f64def848bf in ?? () from /lib/libdbus-1.so.3
#8  0x00007f64ebb6c884 in q_dbus_timeout_handle (this=0xbcc0e0, e=<value optimized out>) at ./qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (this=0xbcc0e0, e=<value optimized out>) at qdbusintegrator.cpp:1023
#10 0x00007f64eac5c353 in QObject::event (this=0xbcc0e0, e=0x0) at kernel/qobject.cpp:1074
#11 0x00007f64eb11b01d in QApplicationPrivate::notify_helper (this=0xbe07a0, receiver=0xbcc0e0, e=0x7fff1b0b69e0) at kernel/qapplication.cpp:4065
#12 0x00007f64eb12307a in QApplication::notify (this=0x7fff1b0b6d20, receiver=0xbcc0e0, e=0x7fff1b0b69e0) at kernel/qapplication.cpp:4030
#13 0x00007f64ec46e0db in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#14 0x00007f64eac4cc9c in QCoreApplication::notifyInternal (this=0x7fff1b0b6d20, receiver=0xbcc0e0, event=0x7fff1b0b69e0) at kernel/qcoreapplication.cpp:610
#15 0x00007f64eac792c6 in QCoreApplication::sendEvent (this=0xbd9140) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (this=0xbd9140) at kernel/qeventdispatcher_unix.cpp:580
#17 0x00007f64eac75658 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 0x00007f64e6ba112a in g_main_dispatch (context=0xbe0e50) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:1960
#20 IA__g_main_context_dispatch (context=0xbe0e50) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:2513
#21 0x00007f64e6ba4988 in g_main_context_iterate (context=0xbe0e50, block=1, dispatch=1, self=<value optimized out>) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:2591
#22 0x00007f64e6ba4b3c in IA__g_main_context_iteration (context=0xbe0e50, may_block=1) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:2654
#23 0x00007f64eac7539c in QEventDispatcherGlib::processEvents (this=0xbb1790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#24 0x00007f64eb1b1f1f in QGuiEventDispatcherGlib::processEvents (this=0x63006900720065, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f64eac4b562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f64eac4b934 in QEventLoop::exec (this=0x7fff1b0b6c90, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f64eac4dba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x000000000043953d in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-01 22:22:48 UTC
Merging with bug 208921. Thanks

*** This bug has been marked as a duplicate of bug 208921 ***
Comment 2 Dario Andres 2009-11-01 22:24:52 UTC
It seems those bugs are related to the Nepomuk integration. Try disabling it (in SystemSettings) to check if the crashes stop. Thanks
Comment 3 Stirling Westrup 2009-11-01 22:28:04 UTC
Thanks. I've disabled Nepomuk and will see if that has any effect.