Version: (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages When starting amarok2, I always get the KDE Crash Handler coming up and notifying me about: The application KDE Daemon (kded4) crashed and caused the signal 6 (SIGABRT). However, I experience no obvious further effects, amarok just runs fine. Here are the details: Application: KDE Daemon (kded4), signal SIGABRT (no debugging symbols found) ... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb61db6c0 (LWP 6674)] (no debugging symbols found) ... (no debugging symbols found) [KCrash handler] #6 0xb7f15410 in __kernel_vsyscall () #7 0xb7dcb085 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7dcca01 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb7497367 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb7497458 in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb7497505 in qt_assert () from /usr/lib/libQtCore.so.4 #12 0xb49239d2 in ?? () from /usr/lib/kde4/lib/kde4/kded_globalaccel.so #13 0xb4928ce6 in ?? () from /usr/lib/kde4/lib/kde4/kded_globalaccel.so #14 0xb4923fef in ?? () from /usr/lib/kde4/lib/kde4/kded_globalaccel.so #15 0xb7313880 in ?? () from /usr/lib/libQtDBus.so.4 #16 0xb7314ad6 in ?? () from /usr/lib/libQtDBus.so.4 #17 0xb73150fc in ?? () from /usr/lib/libQtDBus.so.4 #18 0xb73154aa in ?? () from /usr/lib/libQtDBus.so.4 #19 0xb759ac31 in QObject::event () from /usr/lib/libQtCore.so.4 #20 0xb6af9f9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0xb6afebf9 in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0xb7a08483 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5 #23 0xb758b0b9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0xb758c469 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #25 0xb758c68d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #26 0xb75b662f in ?? () from /usr/lib/libQtCore.so.4 #27 0xb6531cc6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0xb6535083 in ?? () from /usr/lib/libglib-2.0.so.0 #29 0xb653563e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0xb75b69f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #31 0xb6b8da25 in ?? () from /usr/lib/libQtGui.so.4 #32 0xb758a33d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #33 0xb758a4cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #34 0xb758c74d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #35 0xb6af9897 in QApplication::exec () from /usr/lib/libQtGui.so.4 #36 0xb7f0bc12 in kdemain () from /usr/lib/kde4/lib/libkdeinit4_kded4.so #37 0x08048572 in _start () #0 0xb7f15410 in __kernel_vsyscall () Hope that helps anyway.
*** This bug has been marked as a duplicate of bug 174387 ***