amarok hangs on start

Bug #89711 reported by Corey Shields
8
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Fresh install of Kubuntu Feisty Fawn, herd 5, i386 on an AMD Athlon64 FX-53 (yes, purposefully running i386) ;)

When amarok starts, the playlist window is displayed but frozen (sometimes the entire display gets drawn, sometimes just artifacts). Icon is displayed as a "busy" when hovering over the window, and nothing else happens.

dpkg -l "amarok*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii amarok 1.4.5-0ubuntu5 versatile and easy to use audio player for K
un amarok-engine <none> (no description available)
un amarok-engines <none> (no description available)
ii amarok-xine 1.4.5-0ubuntu5 xine engine for the amaroK audio player

I have an strace output of amarokapp (~2.2meg) at:
http://staff.osuosl.org/~cshields/amarok-strace-out.txt

Let me know if I can help in any way here.

Cheers!

Revision history for this message
Corey Shields (cshields) wrote :

skipped my mind to port the output of the app itself, sorry:

amarokapp
QSettings: malformed line '<<<<<<< TREE' in group 'Settings'
QSettings: malformed line '>>>>>>> MERGE-SOURCE' in group 'Settings'
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x809e510 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x809e510 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow

Revision history for this message
Paul Dufresne (paulduf) wrote :

Amarok, when started, just look at the output of dcop, to see if amarokapp is already there. Often, there is one but that is not responsive (dcop amarokapp) hangs.

So, doing:
killall amarok
killall amarokapp
waiting 60 seconds without having sound in KDE to let artsd disable
making sure kaffeine is not working
then launching amarok
open it in the 'program tray' at the right
normally works well for me for making amarok live again.

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

Did Paul's suggestion help any, Corey?

Changed in amarok:
assignee: nobody → ash211
status: Unconfirmed → Needs Info
Revision history for this message
Andrew Ash (ash211) wrote :

Bughelper also reports that this may be related to bug 84967.

Revision history for this message
Corey Shields (cshields) wrote : Re: [Bug 89711] Re: amarok hangs on start

No, it did not (thanks for the ping, got busy and forgot to comment)..
 It shows in the program tray just fine and starts, but still has the
same hanging problem.

I'll look into 84967 when I have a few mins

thanks!

--
Corey Shields - OSU Open Source Lab
One of InfoWorld's Top100 Projects of 2006!
http://osuosl.org

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

How's that looking into coming along, Corey?

Revision history for this message
Miguel Tadeu (mtadeunet) wrote :

The same thing is happening here...here's what I tried with no success at all:

- Paul's solution
- Deleting amarokrc and sppd/amarok/
- Reinstalling all amarok and xine related packages

Any ideas?

thanks

Revision history for this message
David Oxland (doxland) wrote :

I've got the same symptoms.
Just hangs on start up or request for play.
completely uninstalled and installed again.
no change

Fiesty 7.04

Andrew Ash (ash211)
Changed in amarok:
assignee: ash211 → nobody
Revision history for this message
Andrew (andrewkvalheim) wrote :

I'm getting all the same behavior on a new installation of Ubuntu Feisty. Amarok worked fine immediately after installation, but after logging in to another user account it's behaving as reported here. Window draws completely but is unresponsive, mouse pointer hourglasses on hover.

kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8095fb0 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8095fb0 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow

Also, 'killall amarokapp' is unhelpful, reporting 'no process killed'.

Revision history for this message
Michael Ambrus (ambrmi09) wrote :

I'm having the same problem (AmaroK 1.4.3). Removing all AmaroK files from $HOME directory will help (but will also require re-doing the personalised setup). I did the following (killed all running KDE apps first just in case):

 killall amarokapp
 killall dcopserver
 cd .kde/
 find . -iname "*amarok*" -exec rm -rf '{}' ';'

After that AmaroK should start up with the start-up wizard.

Hint:
This maybe somehow related to the play-list management since I've also noticed that AmaroK sometimes looses the setting of the "collection folders". Until this hang bug happened it was harmless and all I had to do was re-entering that setting.

Revision history for this message
Alchera (barrysuridge) wrote :

My problem was only getting the busy icon and nothing appearing any where. I found a solution that worked perfectly: http://kubuntuforums.net/forums/index.php?topic=3085354.0

Revision history for this message
Jeff Mitchell (jefferai) wrote :

Re: Alchera:

You may also want to try using MySQL instead of the built-in Sqlite. Sqlite is pretty good and has gotten better but if the issue is solved by removing the old database file, it may be an issue with a corrupted database (which may not have been caused by Amarok).

Re: Michael Ambrus:

Do you have an ultra-large playlist? The playlist management code wasn't optimized for large (i.e. maybe larger than a few thousand tracks) playlists which meant that you could see exponential time increases. There were a few patches to minimize this. Try upgrading to 1.4.6 (or, soon, 1.4.7) and see if the behavior is different.

Also, it's not AmaroK. It's Amarok. :-)

Revision history for this message
Duncan (launchpad-cricalix) wrote :

I've just encountered this on Kubuntu 7.04, with the addition of the Feisty backports version of Amarok (1.4.7). 1.4.5 was working just fine, closed it out, upgraded, and when it starts up now, it just shows the spinning icon to say 'wait'. Waited 5 minutes, no change. Attempting to close Amarok resulted in a terminate dialog. Whacked anything mentioning amarok in .kde/, tried again. No joy.

kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8099db0 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8099db0 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
        StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has gone wrong?

Revision history for this message
Duncan (launchpad-cricalix) wrote :

Having now downgraded back to 1.4.5, the problem still exists. The downgrade process was as follows:
Remove fiesty backports from sources.list
Remove amarok, amarok-xine
Update the apt database
Install amarok, amarok-xine
Nuke all amarok data in .kde/
Restart X

Amarok 1.4.5 now exhibits the same hanging behaviour. It's loaded the blue panel to the left saying 'Hello' and offering to build a collection, but I can't actually click in the interface. Minimizing and re-opening results in a window with no widgets, just white.

Revision history for this message
Jeff Mitchell (jefferai) wrote :

Andrew:

QSettings: malformed line '<<<<<<< TREE' in group 'Settings'
QSettings: malformed line '>>>>>>> MERGE-SOURCE' in group 'Settings'

Never seen this before, and if downgrading Amarok isn't helping (Duncan) I'm wondering if there's another package everyone upgraded to that's causing the problem.

That looks suspiciously like a cruft from a conflict when doing some sort of a source code update on either qt or Amarok.

Duncan: Are you sure you're getting .kde/share/apps/amarok as well as .kde/share/config/amarokrc as well as .kde/share/config/amarokcollectionscannerrc?

Revision history for this message
Jeff Mitchell (jefferai) wrote :

In fact, after some Googling I can pretty much guarantee that Corey at least is running into a problem that is not inherent to Amarok. Those TREE and MERGE-SOURCE labels are put in by Bazaar, the Canonical SCM system:

https://bugs.launchpad.net/bzr/+bug/36399

So I don't know what file QSettings is complaining about (you may want to do a 'find | xargs grep TREE' in ~/.kde but this problem may be even deeper, down to packages built with badly merged files. Since it seems to be affecting people now running at least three different versions of Amarok, I'm guessing it's a KDE or Qt package.

I'm leaving this in Ubuntu hands. I'll keep watching the thread, but there's nothing I can do about this.

Revision history for this message
Duncan (launchpad-cricalix) wrote :

@Jeff:
Yeah, the find pattern matches anything with amarok in it. Heck, I didn't even have a collection loaded, I was just using Amarok to play a stream.

I have rebooted since my last update, and Amarok 1.4.5 is happy again. I did see a reference in strace to a shared memory operation getting denied, and that's where the strace stopped. Of course, it's working now, so I can't reproduce it. I -think- it was ENOPERM.

Revision history for this message
Jeff Mitchell (jefferai) wrote :

Hmm, well, glad rebooting helped. I'm still very worried about those TREE/MERGE-SOURCE lines. QSettings should *not* be seeing them, AFAICT. Andrew, any comment?

Revision history for this message
p0ssum (pstroud) wrote :

In the process of building an automated backend to run under Xvfb, I ran into this issue, or at least I think it was, I could not see the GUI;-)

Anyhow, I tried removing all of the following:

      rm -rf /tmp/ksocket*
      rm -rf /tmp/kde-paul
      rm -rf /tmp/.X11-unix/[d0-9].*
      rm -rf /tmp/orbit-paul
      rm -rf ~/.DCOP*
      rm -rf /var/tmp/kdecache-paul

and nothing worked, I poured through lsof, netstat, and everything else looking for something I was missing. Here is where the strace hung:
(strace dcop --all-sessions --user paul amarok player isPlaying)

read(5, 0x7ffffac82560, 32) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=5, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(5, "\34\270\t\0\1\0\240\3\4\0\0\0\3168\232\26\0008\232\26\210"..., 32) = 32
write(4, "\1\2\1\0h\0\0\0004\0\0\0", 12) = 12
write(4, "\0\0\0\20anonymous-11008\0\0\0\0\7amarok\0\0"..., 96) = 96
write(4, "\0\0\0\0\26\2328\316", 8) = 8
read(4,

I noticed this was while reading:

access("/home/paul/.Xauthority", R_OK) = 0
open("/home/paul/.Xauthority", O_RDONLY) = 6
fstat(6, {st_mode=S_IFREG|0600, st_size=208, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b4eafe47000
read(6, "\1\0\0\6mythtv\0\00212\0\22MIT-MAGIC-COOKIE"..., 4096) = 208

Once I removed my .Xauthority file, everything was find. Dont know if this helps anyone else, but I figured it was worth a try...

Revision history for this message
Jeff Mitchell (jefferai) wrote :

Are you doing this as part of some MythTV setup?

It seems like DCOP was trying to broadcast out to Amarok, but didn't have the proper permissions to actually do so across X sessions. Not sure whose fault that is...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for amarok (Ubuntu) because there has been no activity for 60 days.]

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.