| Summary: | Dolhin crashes when viewing folders | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | hilbring |
| Component: | general | Assignee: | Peter Penz <peter.penz19> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra |
| Priority: | NOR | ||
| Version: | 16.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Another Qt-dbus crash related to bug 205252 / bug 208921 / bug 205490, which could be Nepomuk integration fault... Thanks *** This bug has been marked as a duplicate of bug 208921 *** |
Application that crashed: dolphin Version of the application: 1.3 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: I open dolphin and doing nothing else. The i wait some time. Dolhin crashes and the error report shows unresolved debug information in libdbus -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #6 0xb5b4101a in ?? () from /lib/libdbus-1.so.3 #7 0xb5b53e35 in ?? () from /lib/libdbus-1.so.3 #8 0xb5b45fe5 in ?? () from /lib/libdbus-1.so.3 #9 0xb5b59092 in dbus_timeout_handle () from /lib/libdbus-1.so.3 #10 0xb727a642 in QDBusConnectionPrivate::timerEvent (this=0x84d35b8, e=0xbfe3d37c) at ./qdbus_symbols_p.h:172 #11 0xb67d816f in QObject::event (this=0x84d35b8, e=0xbfe3d37c) at kernel/qobject.cpp:1075 #12 0xb69ded3c in QApplicationPrivate::notify_helper (this=0x84e19f0, receiver=0x84d35b8, e=0xbfe3d37c) at kernel/qapplication.cpp:4056 #13 0xb69e703e in QApplication::notify (this=0xbfe3d614, receiver=0x84d35b8, e=0xbfe3d37c) at kernel/qapplication.cpp:3603 #14 0xb772649d in KApplication::notify (this=0xbfe3d614, receiver=0x84d35b8, event=0xbfe3d37c) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302 #15 0xb67c7bcb in QCoreApplication::notifyInternal (this=0xbfe3d614, receiver=0x84d35b8, event=0xbfe3d37c) at kernel/qcoreapplication.cpp:610 #16 0xb67f6d51 in QTimerInfoList::activateTimers (this=0x84dd09c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 0xb67f33a0 in timerSourceDispatch (source=0x84dd068) at kernel/qeventdispatcher_glib.cpp:165 #18 0xb5f43b88 in IA__g_main_context_dispatch (context=0x84dc898) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814 #19 0xb5f470eb in g_main_context_iterate (context=0x84dc898, block=1, dispatch=1, self=0x84da300) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448 #20 0xb5f47268 in IA__g_main_context_iteration (context=0x84dc898, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511 #21 0xb67f32f8 in QEventDispatcherGlib::processEvents (this=0x84bcd10, flags={i = -1075587848}) at kernel/qeventdispatcher_glib.cpp:327 #22 0xb6a80a75 in QGuiEventDispatcherGlib::processEvents (this=0x84bcd10, flags={i = -1075587800}) at kernel/qguieventdispatcher_glib.cpp:202 #23 0xb67c61fa in QEventLoop::processEvents (this=0xbfe3d5a0, flags={i = -1075587736}) at kernel/qeventloop.cpp:149 #24 0xb67c6642 in QEventLoop::exec (this=0xbfe3d5a0, flags={i = -1075587672}) at kernel/qeventloop.cpp:201 #25 0xb67c8ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #26 0xb69debb7 in QApplication::exec () at kernel/qapplication.cpp:3525 #27 0x0807aaef in _start () This bug may be a duplicate of or related to bug 210626 Reported using DrKonqi