[Bug 172254] KDED4 crashes at KDE-Start
Heinrich Witt
heinrichwittdo at googlemail.com
Mon Oct 6 08:46:39 BST 2008
http://bugs.kde.org/show_bug.cgi?id=172254
--- Comment #1 from Heinrich Witt <heinrichwittdo googlemail com> 2008-10-06 09:46:37 ---
After install from libqt4-dbg, kdelibs5-dbg and libc6-dbg:
Anwendung: KDE-Dienst (kded4), Signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9cffb00750 (LWP 18205)]
[KCrash handler]
#5 0x00007f9cff4f7145 in raise () from /lib/libc.so.6
#6 0x00007f9cff4f8663 in abort () from /lib/libc.so.6
#7 0x00007f9cfdf6f5a5 in qt_message_output (msgType=QtFatalMsg,
buf=<value optimized out>) at global/qglobal.cpp:2102
#8 0x00007f9cfdf6f6e7 in qFatal (msg=<value optimized out>)
at global/qglobal.cpp:2303
#9 0x00007f9cf4285a88 in KdedGlobalAccel::setShortcut (this=0xaf13b0,
actionId=<value optimized out>, keys=@0xaef530,
flags=<value optimized out>)
at /tmp/buildd/kde4libs-4.1.2/kdeui/shortcuts/kdedglobalaccel.cpp:412
#10 0x00007f9cf4285cc2 in KdedGlobalAccelAdaptor::qt_metacall (this=0xb7d310,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>,
_a=0x7fff07c44d80)
at /tmp/buildd/kde4libs-4.1.2/kdeui/shortcuts/kdedglobalaccel_adaptor.h:76
#11 0x00007f9cfe36bdb3 in QDBusConnectionPrivate::deliverCall (this=0x90f610,
object=0xb7d310, msg=@0xb1f6c0, metaTypes=@0x919ee0, slotIdx=13)
at qdbusintegrator.cpp:849
#12 0x00007f9cfe36d0c0 in QDBusConnectionPrivate::activateCall (this=0x90f610,
object=0xb7d310, flags=337, msg=@0xb1f6c0) at qdbusintegrator.cpp:761
#13 0x00007f9cfe36d6a1 in QDBusConnectionPrivate::activateObject (
this=0x90f610, node=@0xb1f698, msg=@0xb1f6c0,
pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1283
#14 0x00007f9cfe36d9b8 in QDBusActivateObjectEvent::placeMetaCall (
this=0xb1f650) at qdbusintegrator.cpp:1400
#15 0x00007f9cfe06e345 in QObject::event (this=0xaf13b0, e=0xb1f650)
at kernel/qobject.cpp:1155
#16 0x00007f9cfd277a5d in QApplicationPrivate::notify_helper (this=0x91f120,
receiver=0xaf13b0, e=0xb1f650) at kernel/qapplication.cpp:3803
#17 0x00007f9cfd27f7da in QApplication::notify (this=0x7fff07c45d00,
receiver=0xaf13b0, e=0xb1f650) at kernel/qapplication.cpp:3768
#18 0x00007f9cfec2841b in KApplication::notify (this=0x7fff07c45d00,
receiver=0xaf13b0, event=0xb1f650)
at /tmp/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
#19 0x00007f9cfe05f381 in QCoreApplication::notifyInternal (
this=0x7fff07c45d00, receiver=0xaf13b0, event=0xb1f650)
at kernel/qcoreapplication.cpp:587
#20 0x00007f9cfe06001a in QCoreApplicationPrivate::sendPostedEvents (
receiver=0x0, event_type=0, data=0x8fbde0)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#21 0x00007f9cfe087a83 in postEventSourceDispatch (s=<value optimized out>)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:214
#22 0x00007f9cfa15eacb in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#23 0x00007f9cfa16228d in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007f9cfa16244b in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#25 0x00007f9cfe08770f in QEventDispatcherGlib::processEvents (this=0x91f300,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319
#26 0x00007f9cfd30944f in QGuiEventDispatcherGlib::processEvents (this=0x471d,
flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198
#27 0x00007f9cfe05dca2 in QEventLoop::processEvents (
this=<value optimized out>, flags={i = 130308912})
at kernel/qeventloop.cpp:143
#28 0x00007f9cfe05de2d in QEventLoop::exec (this=0x7fff07c45b70, flags=
{i = 130308992}) at kernel/qeventloop.cpp:194
#29 0x00007f9cfe0602dd in QCoreApplication::exec ()
at kernel/qcoreapplication.cpp:845
#30 0x00007f9cff824f0a in kdemain (argc=1, argv=0x7fff07c46138)
at /tmp/buildd/kde4libs-4.1.2/kded/kded.cpp:847
#31 0x00007f9cff4e3466 in __libc_start_main () from /lib/libc.so.6
#32 0x0000000000400629 in _start ()
#0 0x00007f9cff564170 in __nanosleep_nocancel () from /lib/libc.so.6
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list