Summary: | Crash after using Krunner | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Fabian <0inkane> |
Component: | kded | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Chakra | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Better backtrace |
Description
Fabian
2013-01-23 21:54:50 UTC
Hm, I (probably) got this crash again, and having restarted kded before from konsole, it printed process 2910: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2603. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Created attachment 76864 [details]
Better backtrace
This is a backtrace with slightly more information. Also, kded4 started from console printed
process 23787: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2603.
This is normally a bug in some application using the D-Bus library.
/usr/lib/libdbus-1.so.3(+0x56bea) [0x7fd29b761bea]
/usr/lib/libdbus-1.so.3(+0x5a349) [0x7fd29b765349]
/usr/lib/libdbus-1.so.3(+0x4266c) [0x7fd29b74d66c]
/usr/lib/libdbus-1.so.3(dbus_message_iter_append_basic+0xaf) [0x7fd29b730f4f]
/usr/lib/libQtDBus.so.4(+0x5664e) [0x7fd29f8de64e]
/usr/lib/libQtDBus.so.4(+0x2e500) [0x7fd29f8b6500]
/usr/lib/libQtDBus.so.4(+0x1c153) [0x7fd29f8a4153]
/usr/lib/libQtDBus.so.4(+0x23951) [0x7fd29f8ab951]
/usr/lib/libQtDBus.so.4(+0x249f5) [0x7fd29f8ac9f5]
/usr/lib/libQtDBus.so.4(+0x25396) [0x7fd29f8ad396]
/usr/lib/libQtDBus.so.4(+0x2548b) [0x7fd29f8ad48b]
/usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x26e) [0x7fd29f53236e]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xb1) [0x7fd2a01a6021]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x239) [0x7fd2a01ab0f9]
/usr/lib/libkdeui.so.5(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x36) [0x7fd2a0f69256]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e) [0x7fd29f51b7ee]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x308) [0x7fd29f51f198]
/usr/lib/libQtCore.so.4(+0x1b9e03) [0x7fd29f54ce03]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x13c) [0x7fd29cb3eeac]
/usr/lib/libglib-2.0.so.0(+0x472c8) [0x7fd29cb3f2c8]
/usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x34) [0x7fd29cb3f384]
/usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66) [0x7fd29f54cf96]
/usr/lib/libQtGui.so.4(+0x27a54e) [0x7fd2a025354e]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7fd29f519d2f]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x108) [0x7fd29f519f88]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x88) [0x7fd29f51f5a8]
/usr/lib/libkdeinit4_kded4.so(kdemain+0x880) [0x7fd2a1a6e2e0]
/lib/libc.so.6(__libc_start_main+0xf5) [0x7fd2a16e6455]
kded4() [0x400651]
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
sock_file=/home/fabian/.kde4/socket-HOSTNAMEchakra-pc/kdeinit4__0
KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/fabian/.kde4/socket-HOSTNAMEchakra-pc/kdeinit4__0
It seems that the error is related to Appmenu, and seems to happen only on upgrade. Setting this to needsinfo downstream, until it is clear what kind of bug this is. |