Comment 2 for bug 89711

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.