Bug 180820 - Amarok crashed and caused the signal 6 (SIGABRT) after plug in USB drive
Summary: Amarok crashed and caused the signal 6 (SIGABRT) after plug in USB drive
Status: RESOLVED DUPLICATE of bug 160221
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: Kevin Ottens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-15 15:30 UTC by Sigh Monk
Modified: 2009-01-16 11:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sigh Monk 2009-01-15 15:30:40 UTC
Version:           2.0.1 (using KDE 4.1.3)
Installed from:    Ubuntu Packages

I'm using Intrepid and using Kubuntu Members launchpad repo.
Whenever I plug in the USB drive, amarok will crash.
Affect the older 2.0 too.

Backtrace:
Application: Amarok (amarok), signal SIGABRT

[Thread debugging using libthread_db enabled]
[New Thread 0xb49ca6c0 (LWP 30859)]
[New Thread 0x9ffffb90 (LWP 31284)]
[New Thread 0xa39eab90 (LWP 31283)]
[New Thread 0xa5f3cb90 (LWP 31282)]
[New Thread 0xa2dffb90 (LWP 31281)]
[New Thread 0xa4deeb90 (LWP 31280)]
[New Thread 0xa0bd4b90 (LWP 30890)]
[New Thread 0xa15fcb90 (LWP 30887)]
[New Thread 0xa1dfdb90 (LWP 30886)]
[New Thread 0xa25feb90 (LWP 30885)]
[New Thread 0xa41ebb90 (LWP 30881)]
[New Thread 0xa55efb90 (LWP 30879)]
[New Thread 0xb1f3ab90 (LWP 30866)]
[New Thread 0xb273cb90 (LWP 30863)]
[New Thread 0xb2f3db90 (LWP 30861)]

[KCrash handler]
#6  0xb80e1430 in __kernel_vsyscall ()
#7  0xb6b25880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6b27248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7ed3795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7ed3872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7ed3915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb5c5e54a in ?? () from /usr/lib/libsolid.so.4
#13 0xb5c5e84f in ?? () from /usr/lib/libsolid.so.4
#14 0xb7fe0a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7fe17e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb5c70853 in ?? () from /usr/lib/libsolid.so.4
#17 0xb5c9646e in ?? () from /usr/lib/libsolid.so.4
#18 0xb5c9655a in ?? () from /usr/lib/libsolid.so.4
#19 0xb678d26e in ?? () from /usr/lib/libQtDBus.so.4
#20 0xb6794627 in ?? () from /usr/lib/libQtDBus.so.4
#21 0xb7fdb771 in QObject::event () from /usr/lib/libQtCore.so.4
#22 0xb74a28ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#23 0xb74aa72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#24 0xb71cab2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#25 0xb7fcbe61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#26 0xb7fccae5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb7fcccdd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb7ff682f in ?? () from /usr/lib/libQtCore.so.4
#29 0xb6a566f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb6a59da3 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb6a59f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb7ff6478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#33 0xb753cea5 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb7fca52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb7fca6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0xb7fccda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0xb74a2767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0x0804c042 in _start ()
#0  0xb80e1430 in __kernel_vsyscall ()
Comment 1 Mark Kretschmann 2009-01-15 15:42:56 UTC
Sorry, this backtrace is invalid. Please read this document:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Andrew Ramage 2009-01-15 18:13:35 UTC
I have experienced this for a long time.  (Amarok on openSUSE 10.3, KDE 3.5.7)  But for me the crash happened if I did not cancel the "Handle Device" dialog before unplugging an USB device - could be a Nokia 770 or an SD card placed in the reader, etc.
Comment 3 Abe L. Rhodes 2009-01-16 09:48:29 UTC
I got exactly the same problem,
this is the backtrace,

Application: Amarok (amarok), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb48246c0 (LWP 26950)]
[New Thread 0xa0effb90 (LWP 26973)]
[New Thread 0xa183ab90 (LWP 26971)]
[New Thread 0xa203bb90 (LWP 26970)]
[New Thread 0xa283cb90 (LWP 26969)]
[New Thread 0xa303db90 (LWP 26968)]
[New Thread 0xa383eb90 (LWP 26967)]
[New Thread 0xa403fb90 (LWP 26966)]
[New Thread 0xa4a41b90 (LWP 26964)]
[New Thread 0xa5443b90 (LWP 26963)]
[New Thread 0xa5c44b90 (LWP 26962)]
[New Thread 0xb1bfdb90 (LWP 26961)]
[New Thread 0xb23ffb90 (LWP 26954)]
[New Thread 0xb2d97b90 (LWP 26952)]
[KCrash handler]
#6  0xb7f3b430 in __kernel_vsyscall ()
#7  0xb697f880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6981248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7d2d795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7d2d872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7d2d915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb5ab854a in Solid::DeviceManagerPrivate::_k_deviceAdded (
    this=0x8c43d98, udi=@0x93761e8)
    at /build/buildd/kde4libs-4.1.3/solid/solid/devicemanager.cpp:164
#13 0xb5ab884f in Solid::DeviceManagerPrivate::qt_metacall (this=0x8c43d98, 
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf93c09c)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/solid/solid/devicemanager_p.moc:72
#14 0xb7e3aa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7e3b7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb5aca853 in Solid::Ifaces::DeviceManager::deviceAdded (this=0x8c47188, 
    _t1=@0x93761e8)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/solid/solid/ifaces/devicemanager.moc:79
#17 0xb5af046e in Solid::Backends::Hal::HalManager::slotDeviceAdded (
    this=0x8c47188, udi=@0x93761e8)
    at /build/buildd/kde4libs-4.1.3/solid/solid/backends/hal/halmanager.cpp:214
#18 0xb5af055a in Solid::Backends::Hal::HalManager::qt_metacall (
    this=0x8c47188, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf93c258)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/solid/solid/backends/hal/halmanager.moc:70
#19 0xb65e726e in ?? () from /usr/lib/libQtDBus.so.4
#20 0xb65ee627 in ?? () from /usr/lib/libQtDBus.so.4
#21 0xb7e35771 in QObject::event () from /usr/lib/libQtCore.so.4
#22 0xb72fc8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#23 0xb730472e in QApplication::notify () from /usr/lib/libQtGui.so.4
#24 0xb7024b2d in KApplication::notify (this=0xbf93c974, receiver=0x8c47188, 
    event=0x9376260)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#25 0xb7e25e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#26 0xb7e26ae5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb7e26cdd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb7e5082f in ?? () from /usr/lib/libQtCore.so.4
#29 0xb68b06f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb68b3da3 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb68b3f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb7e50478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#33 0xb7396ea5 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb7e2452a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb7e246ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0xb7e26da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0xb72fc767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0x0804c042 in main (argc=1, argv=0xbf93ce74)
    at /build/buildd/amarok-kde4-2.0.1.1/src/main.cpp:130
#0  0xb7f3b430 in __kernel_vsyscall ()
Comment 4 Mark Kretschmann 2009-01-16 10:59:47 UTC
This crash appears to be in Solid (a KDE component), so I'm reassigning.
Comment 5 Kevin Ottens 2009-01-16 11:43:44 UTC

*** This bug has been marked as a duplicate of bug 160221 ***