Version: (using KDE 4.1.2) Compiler: GCC 4.1.2 Target: x86_64-unknown-linux-gnu Configured with: ../gcc-4.1.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++ --disable-multilib Thread model: posix OS: Linux Installed from: Compiled From Sources Sometimes when I start any KDE application (I've noticed for amarok and kcalc) the message saying kded4 crashed appears. It makes no problem, application starts successfully and no changes to the whole system, but such a message appears.
Here's crash report: Приложение: Служба KDE (kded4), сигнал SIGABRT Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x7f005771c700 (LWP 3632)] [KCrash handler] #5 0x00007f00537b255b in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:67 #6 0x00007f00537b390e in *__GI_abort () at abort.c:88 #7 0x00007f0056068f95 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2102 #8 0x00007f00560690c7 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2303 #9 0x00007f004be98bf0 in KdedGlobalAccel::setShortcut (this=0x26e23e0, actionId=@0x2552460, keys=@0x2735470, flags=2) at /usr/src/packages/kde4/4.1.2/kdelibs-4.1.2/kdeui/shortcuts/kdedglobalaccel.cpp:412 #10 0x00007f004be9ee27 in KdedGlobalAccelAdaptor::setShortcut (this=0x27098a0, actionId=@0x2552460, keys=@0x2735470, flags=2) at /usr/src/packages/kde4/4.1.2/kdelibs-4.1.2/kdeui/shortcuts/kdedglobalaccel_adaptor.h:76 #11 0x00007f004be99de5 in KdedGlobalAccelAdaptor::qt_metacall (this=0x27098a0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fff5f753b50) at /usr/src/packages/kde4/4.1.2/kdelibs-4.1.2/build/kdeui/kdedglobalaccel_adaptor.moc:115 #12 0x00007f0055245ca6 in QDBusConnectionPrivate::deliverCall (this=0x24dbff0, object=0x27098a0, msg=@0x290c1a0, metaTypes=@0x26fbbb0, slotIdx=13) at qdbusintegrator.cpp:849 #13 0x00007f0055246875 in QDBusConnectionPrivate::activateCall ( this=0x24dbff0, object=0x27098a0, flags=337, msg=@0x290c1a0) at qdbusintegrator.cpp:761 #14 0x00007f0055247062 in QDBusConnectionPrivate::activateObject ( this=0x24dbff0, node=@0x290c178, msg=@0x290c1a0, pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1283 #15 0x00007f00552472a8 in QDBusActivateObjectEvent::placeMetaCall ( this=0x290c130) at qdbusintegrator.cpp:1400 #16 0x00007f005615d612 in QObject::event (this=0x26e23e0, e=0x290c130) at kernel/qobject.cpp:1146 #17 0x00007f005452e77e in QApplicationPrivate::notify_helper (this=0x24e80a0, receiver=0x26e23e0, e=0x290c130) at kernel/qapplication.cpp:3803 #18 0x00007f005453329e in QApplication::notify (this=0x7fff5f7549a0, receiver=0x26e23e0, e=0x290c130) at kernel/qapplication.cpp:3768 #19 0x00007f0056e6c1a8 in KApplication::notify (this=0x7fff5f7549a0, receiver=0x26e23e0, event=0x290c130) at /usr/src/packages/kde4/4.1.2/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311 #20 0x00007f005614eb28 in QCoreApplication::notifyInternal ( this=0x7fff5f7549a0, receiver=0x26e23e0, event=0x290c130) at kernel/qcoreapplication.cpp:587 #21 0x00007f005614fd0d in QCoreApplicationPrivate::sendPostedEvents ( receiver=0x0, event_type=0, data=0x24a3de0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #22 0x00007f0056177513 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:214 #23 0x00007f0052dc2cc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x00007f0052dc34f2 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #25 0x00007f0052dc39a8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x00007f00561777fe in QEventDispatcherGlib::processEvents (this=0x24e8280, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #27 0x00007f00545b4fdf in QGuiEventDispatcherGlib::processEvents (this=0xe30, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198 #28 0x00007f005614df45 in QEventLoop::processEvents ( this=<value optimized out>, flags=@0x7fff5f754800) at kernel/qeventloop.cpp:143 #29 0x00007f005614e0a8 in QEventLoop::exec (this=0x7fff5f754840, flags=@0x7fff5f754850) at kernel/qeventloop.cpp:194 #30 0x00007f00561500ae in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #31 0x00007f005752f27f in kdemain (argc=1, argv=0x7fff5f754d48) at /usr/src/packages/kde4/4.1.2/kdelibs-4.1.2/kded/kded.cpp:847 #32 0x0000000000400843 in main (argc=1, argv=0x7fff5f754d48) at /usr/src/packages/kde4/4.1.2/kdelibs-4.1.2/build/kded/kded4_dummy.cpp:3 #0 0x00007f00538169b0 in __nanosleep_nocancel () from /lib/libc.so.6
I've evaluated, that this take place only when starting Amarok2-beta2. Should this bug be reassigned to Amarok?
*** This bug has been marked as a duplicate of bug 171870 ***