Summary: | dolphin random crash (it seems to be a dbus bug). | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Davide Bettio <davide.bettio> |
Component: | general | Assignee: | Peter Penz <peter.penz19> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, decamps |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Davide Bettio
2009-11-14 13:58:27 UTC
@Davide: we are merging all this kind of Dolphin qt-dbus reports at bug 208921, with the idea that they are Nepomuk related. - Do you have Nepomuk enabled ? (with any special configuration or just the default one?) Thanks I have an extremely similar bug, and indeed neponuk has been activated recently: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #6 _dbus_connection_lock (connection=0x1) at dbus-connection.c:355 #7 0xb51ba005 in _dbus_pending_call_get_connection_and_lock (pending=0xa2052a0) at dbus-pending-call.c:307 #8 0xb51aa8f6 in reply_handler_timeout (data=0xa2052a0) at dbus-connection.c:3156 #9 0xb51beef0 in dbus_timeout_handle (timeout=0xa1e3368) at dbus-timeout.c:473 #10 0xb6b95ec0 in ?? () from /usr/lib/libQtDBus.so.4 Bug 208921 is now fixed. Thanks *** This bug has been marked as a duplicate of bug 208921 *** |