Bug 171666 - Amarok crashes on attach of USB storage
Summary: Amarok crashes on attach of USB storage
Status: RESOLVED DUPLICATE of bug 160221
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.1
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-25 22:40 UTC by Andreas Hermann Braml
Modified: 2008-11-02 16:47 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 Andreas Hermann Braml 2008-09-25 22:40:28 UTC
Version:           1.90 (using KDE 4.1.1)
Installed from:    Ubuntu Packages

Amarok crashes as soon as I attach USB storage.

How to reproduce:
- start Amarok
- attach mass storage device to the USB

I use packages from the Ubuntu kubuntu-members-kde4 PPA for Hardy Heron i386.

Backtrace:

Anwendung: Amarok (amarok), Signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb4952720 (LWP 6881)]
[New Thread 0xaeaacb90 (LWP 6948)]
[New Thread 0xb0559b90 (LWP 6946)]
[New Thread 0xafd58b90 (LWP 6945)]
[New Thread 0xb0f83b90 (LWP 6915)]
[New Thread 0xb1784b90 (LWP 6914)]
[New Thread 0xb1fc7b90 (LWP 6913)]
[New Thread 0xb282ab90 (LWP 6897)]
[KCrash handler]
#6  0xb7ef0410 in __kernel_vsyscall ()
#7  0xb6a48085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6a49a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb74eb367 in qt_message_output (msgType=QtFatalMsg, 
    buf=0xbfff99bc "ASSERT: \"dev->backendObject()==0\" in file /build/buildd/kde4libs-4.1.1+really4.1.1/solid/solid/devicemanager.cpp, line 164")
    at global/qglobal.cpp:2061
#10 0xb74eb458 in qFatal (msg=0xb7632498 "ASSERT: \"%s\" in file %s, line %d")
    at global/qglobal.cpp:2263
#11 0xb74eb505 in qt_assert (assertion=0xb564b3f1 "dev->backendObject()==0", 
    file=0xb564b4d8 "/build/buildd/kde4libs-4.1.1+really4.1.1/solid/solid/devicemanager.cpp", line=164) at global/qglobal.cpp:1831
#12 0xb561469a in Solid::DeviceManagerPrivate::_k_deviceAdded (
    this=0x814ea80, udi=@0x87dce18)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/solid/solid/devicemanager.cpp:164
#13 0xb56147bb in Solid::DeviceManagerPrivate::qt_metacall (this=0x814ea80, 
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfffbafc)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/solid/solid/devicemanager_p.moc:72
#14 0xb75f3f79 in QMetaObject::activate (sender=0x81bbc70, 
    from_signal_index=4, to_signal_index=4, argv=0xbfffbafc)
    at kernel/qobject.cpp:3016
#15 0xb75f4642 in QMetaObject::activate (sender=0x81bbc70, m=0xb5656078, 
    local_signal_index=0, argv=0xbfffbafc) at kernel/qobject.cpp:3086
#16 0xb5626a23 in Solid::Ifaces::DeviceManager::deviceAdded (this=0x81bbc70, 
    _t1=@0x87dce18)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/solid/solid/ifaces/devicemanager.moc:79
#17 0xb5641a7e in Solid::Backends::Hal::HalManager::slotDeviceAdded (
    this=0x81bbc70, udi=@0x87dce18)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/solid/solid/backends/hal/halmanager.cpp:214
#18 0xb5641aed in Solid::Backends::Hal::HalManager::qt_metacall (
    this=0x81bbc70, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfffbcac)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/solid/solid/backends/hal/halmanager.moc:70
#19 0xb53ea880 in QDBusConnectionPrivate::deliverCall (this=0x81bbee0, 
    object=0x81bbc70, msg=@0x87aebac, metaTypes=@0x87aebb0, slotIdx=6)
    at qdbusintegrator.cpp:865
#20 0xb53f3137 in QDBusCallDeliveryEvent::placeMetaCall (this=0x87aeb80, 
    object=0x81bbc70) at qdbusintegrator_p.h:136
#21 0xb75eec31 in QObject::event (this=0x81bbc70, e=0x87aeb80)
    at kernel/qobject.cpp:1140
#22 0xb6ca5f9c in QApplicationPrivate::notify_helper (this=0x8071568, 
    receiver=0x81bbc70, e=0x87aeb80) at kernel/qapplication.cpp:3800
#23 0xb6caabf9 in QApplication::notify (this=0xbfffc44c, receiver=0x81bbc70, 
    e=0x87aeb80) at kernel/qapplication.cpp:3392
#24 0xb7a711c3 in KApplication::notify (this=0xbfffc44c, receiver=0x81bbc70, 
    event=0x87aeb80)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#25 0xb75df0b9 in QCoreApplication::notifyInternal (this=0xbfffc44c, 
    receiver=0x81bbc70, event=0x87aeb80) at kernel/qcoreapplication.cpp:591
#26 0xb75e0469 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x8052558)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#27 0xb75e068d in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qcoreapplication.cpp:1095
#28 0xb760a62f in postEventSourceDispatch (s=0x8073ca0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#29 0xb4fcedd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb4fd2193 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb4fd274e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb760a9f8 in QEventDispatcherGlib::processEvents (this=0x806d1e0, 
    flags=@0xbfffc348) at kernel/qeventdispatcher_glib.cpp:325
#33 0xb6d39a25 in QGuiEventDispatcherGlib::processEvents (this=0x806d1e0, 
    flags=@0xbfffc378) at kernel/qguieventdispatcher_glib.cpp:204
#34 0xb75de33d in QEventLoop::processEvents (this=0xbfffc3f0, 
    flags=@0xbfffc3b4) at kernel/qeventloop.cpp:149
#35 0xb75de4cd in QEventLoop::exec (this=0xbfffc3f0, flags=@0xbfffc3f8)
    at kernel/qeventloop.cpp:200
#36 0xb75e074d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849
#37 0xb6ca5897 in QApplication::exec () at kernel/qapplication.cpp:3330
#38 0x0804b3ca in main (argc=3, argv=0xbfffc934)
    at /build/buildd/amarok-kde4-1.90/src/main.cpp:127
#0  0xb7ef0410 in __kernel_vsyscall ()
Comment 1 Seb Ruiz 2008-10-29 04:48:20 UTC
Looks like a crash in solid. Reassigning.
Comment 2 Oliver Putz 2008-11-02 16:47:53 UTC
It actually looks (and sounds) very much like bug #160221

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