Version: (using KDE 4.1.1) OS: Linux Installed from: Ubuntu Packages Application: KMix (kmix), signal SIGABRT (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f049aa177a0 (LWP 5962)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0x00007f049a296095 in raise () from /lib/libc.so.6 #6 0x00007f049a297af0 in abort () from /lib/libc.so.6 #7 0x00007f0498fb9055 in qt_message_output () from /usr/lib/libQtCore.so.4 #8 0x00007f0498fb919d in qFatal () from /usr/lib/libQtCore.so.4 #9 0x00007f04997e9e89 in ?? () from /usr/lib/kde4/lib/libsolid.so.4 #10 0x00007f04997e9f7f in ?? () from /usr/lib/kde4/lib/libsolid.so.4 #11 0x00007f04990b68b6 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0x00007f04997f88f2 in ?? () from /usr/lib/kde4/lib/libsolid.so.4 #13 0x00007f049980feb1 in ?? () from /usr/lib/kde4/lib/libsolid.so.4 #14 0x00007f0498d0b243 in ?? () from /usr/lib/libQtDBus.so.4 #15 0x00007f0498d136ff in ?? () from /usr/lib/libQtDBus.so.4 #16 0x00007f04990b1497 in QObject::event () from /usr/lib/libQtCore.so.4 #17 0x00007f04980ffacf in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #18 0x00007f0498101c85 in QApplication::notify () from /usr/lib/libQtGui.so.4 #19 0x00007f0499e89ea1 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5 #20 0x00007f04990a26b9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #21 0x00007f04990a39db in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #22 0x00007f04990cb6e3 in ?? () from /usr/lib/libQtCore.so.4 #23 0x00007f049576f3d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x00007f04957726e5 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0x00007f0495772bcb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x00007f04990cb9df in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #27 0x00007f049818920f in ?? () from /usr/lib/libQtGui.so.4 #28 0x00007f04990a1b35 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #29 0x00007f04990a1c8b in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #30 0x00007f04990a3cd9 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #31 0x00007f049a5ea4df in kdemain () from /usr/lib/kde4/lib/libkdeinit4_kmix.so #32 0x00007f049a2821c4 in __libc_start_main () from /lib/libc.so.6 #33 0x0000000000400649 in _start () #0 0x00007f049a301b50 in nanosleep () from /lib/libc.so.6
For the records: Not exactly sure if this bug was not reported a little too early for this, but is it possible that this one is the same crash as bug #174037?
My MKix just crashed. Kubuntu 64-bit KDE 4.1.3. I was doing nothing at all. Just listening to music with amarok 1.4.10, as I have been for the past couple of hours. Here is the backtrace with debugging symbols: ---- Application: KMix (kmix), signal SIGABRT (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f9dc5fbc6f0 (LWP 6694)] [KCrash handler] #5 0x00007f9dc5833fd5 in raise () from /lib/libc.so.6 #6 0x00007f9dc5835b43 in abort () from /lib/libc.so.6 #7 0x00007f9dc45036b5 in qt_message_output () from /usr/lib/libQtCore.so.4 #8 0x00007f9dc45037fd in qFatal () from /usr/lib/libQtCore.so.4 #9 0x00007f9dc4d5c323 in Solid::DeviceManagerPrivate::_k_deviceAdded ( this=0x9a0e20, udi=@0x9b2140) at /build/buildd/kde4libs-4.1.3/solid/solid/devicemanager.cpp:164 #10 0x00007f9dc4d5c637 in Solid::DeviceManagerPrivate::qt_metacall ( this=0x9a0e20, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffcdfeb7b0) at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/solid/solid/devicemanager_p.moc:72 #11 0x00007f9dc4608134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0x00007f9dc4d6bcc2 in Solid::Ifaces::DeviceManager::deviceAdded ( this=0x1a26, _t1=<value optimized out>) at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/solid/solid/ifaces/devicemanager.moc:79 #13 0x00007f9dc4d8e86c in Solid::Backends::Hal::HalManager::qt_metacall ( this=0x996f70, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffcdfeba90) at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/solid/solid/backends/hal/halmanager.moc:70 #14 0x00007f9dc4253ea3 in ?? () from /usr/lib/libQtDBus.so.4 #15 0x00007f9dc425aeef in ?? () from /usr/lib/libQtDBus.so.4 #16 0x00007f9dc4602da5 in QObject::event () from /usr/lib/libQtCore.so.4 #17 0x00007f9dc365ec3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #18 0x00007f9dc36669ba in QApplication::notify () from /usr/lib/libQtGui.so.4 #19 0x00007f9dc5427fcb in KApplication::notify (this=0x84f2c0, receiver=0x996f70, event=0xc48020) at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311 #20 0x00007f9dc45f3d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #21 0x00007f9dc45f49fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #22 0x00007f9dc461c4d3 in ?? () from /usr/lib/libQtCore.so.4 #23 0x00007f9dc0cbad3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x00007f9dc0cbe50d in ?? () from /usr/lib/libglib-2.0.so.0 #25 0x00007f9dc0cbe6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x00007f9dc461c15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #27 0x00007f9dc36f0a6f in ?? () from /usr/lib/libQtGui.so.4 #28 0x00007f9dc45f2682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #29 0x00007f9dc45f280d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #30 0x00007f9dc45f4cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #31 0x00007f9dc5b8f52a in kdemain () from /usr/lib/libkdeinit4_kmix.so #32 0x00007f9dc581f466 in __libc_start_main () from /lib/libc.so.6 #33 0x0000000000400659 in _start () #0 0x00007f9dc58a95f0 in __nanosleep_nocancel () from /lib/libc.so.6
Moved to kmix
Backtrace in comment 2 looks like the one in bug 160221. We don't know if the original bug report backtrace coincides with the one described on comment 2.
I can't swear to it (it's too long ago now), but I think it was quite likely that in the period before the kmix crash I had added and then removed a USB stick. So the crash I experienced could well be the same crash as bug 160221 (although why the crash was in kmix I have no idea).
*** This bug has been marked as a duplicate of bug 160221 ***