Amarok crashed on startup in libamarok_massstorage-device

Bug #410027 reported by Dima Ryazanov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: amarok

I'm running Kubuntu Jaunty. After upgrading to KDE 4.3 and Amarok 2.1.0 from http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu, Amarok crashed on startup:

Thread 1 (Thread 0x7f0fc75da790 (LWP 9996)):
[KCrash Handler]
#5 0x00007f0fa8e16750 in ?? () from /usr/lib/kde4/libamarok_massstorage-device.so
#6 0x00007f0fc6be151c in ?? () from /usr/lib/libamaroklib.so.1
#7 0x00007f0fc6be4b6b in ?? () from /usr/lib/libamaroklib.so.1
#8 0x00007f0fc6be4f05 in ?? () from /usr/lib/libamaroklib.so.1
#9 0x00007f0fc6be4f9d in MountPointManager::instance () from /usr/lib/libamaroklib.so.1
#10 0x00007f0faa04d6af in ?? () from /usr/lib/kde4/libamarok_collection-sqlcollection.so
#11 0x00007f0faa03c875 in ?? () from /usr/lib/kde4/libamarok_collection-sqlcollection.so
#12 0x00007f0faa05f2f9 in ?? () from /usr/lib/kde4/libamarok_collection-sqlcollection.so
#13 0x00007f0faa08a6ed in ?? () from /usr/lib/kde4/libamarok_collection-sqlcollection.so
#14 0x00007f0faa05f050 in ?? () from /usr/lib/kde4/libamarok_collection-sqlcollection.so
#15 0x00007f0fc6a67975 in CollectionManager::init () from /usr/lib/libamaroklib.so.1
#16 0x00007f0fc6a681cd in CollectionManager::instance () from /usr/lib/libamaroklib.so.1
#17 0x00007f0fc69e3e7d in ServiceFactory::ServiceFactory () from /usr/lib/libamaroklib.so.1
#18 0x00007f0faa2b7096 in create_plugin () from /usr/lib/kde4/amarok_service_shoutcast.so
#19 0x00007f0fc6b5692f in ?? () from /usr/lib/libamaroklib.so.1
#20 0x00007f0fc69fb729 in ?? () from /usr/lib/libamaroklib.so.1
#21 0x00007f0fc69fc21d in ?? () from /usr/lib/libamaroklib.so.1
#22 0x00007f0fc6988dda in Playlist::Model::Model () from /usr/lib/libamaroklib.so.1
#23 0x00007f0fc698990d in Playlist::Model::instance () from /usr/lib/libamaroklib.so.1
#24 0x00007f0fc6af0736 in StatusBar::StatusBar () from /usr/lib/libamaroklib.so.1
#25 0x00007f0fc6b4b26e in MainWindow::MainWindow () from /usr/lib/libamaroklib.so.1
#26 0x00007f0fc6b2d377 in App::continueInit () from /usr/lib/libamaroklib.so.1
#27 0x00007f0fc6b2e2ab in App::App () from /usr/lib/libamaroklib.so.1
#28 0x000000000053305b in _start ()

No debug symbols until you guys fix bug 368470.

Revision history for this message
Andrew Ash (ash211) wrote :

I'm not sure how you ended up with the kubuntu-ppa backports, but the official backports[1] are the recommended way for running the latest Amarok now. Confusing I know, and I only just recently found out that this is the preferred method and don't know of the right place to make that information clear.

Please try this version and report back with whether this issue still exists and the exact version you're using (''apt-cache policy amarok''). Thanks!

[1] https://help.ubuntu.com/community/UbuntuBackports

Changed in amarok (Ubuntu):
status: New → Incomplete
Revision history for this message
Dima Ryazanov (dima-gmail) wrote :

Oh interesting... I got my URL from http://www.kubuntu.org/

Revision history for this message
Andrew Ash (ash211) wrote :

You're right, I was a bit surprised too. But backports has 2.1.1 and the PPA only 2.1.0 so that's my interpretation of the reason for the recommendation now. Here's a comment by an Amarok upstream representative [1].

[1] https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/357375/comments/3

Revision history for this message
Jmadero (jmadero) wrote :

I'm having this problem with 2.1.1 in Jaunty...anyone have luck fixing it?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

If this is still an issue with Kubuntu 2.2 in Kubuntu 9.10, could somebody install amarok-dbg and get a new backtrace please?

Changed in amarok (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in amarok (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.