I doubt this issue is caused by amarok. Its symptoms are eerily similar to the well known ALSA issue where one application greedily hogs *hw:* instead of using default (PulseAudio is configured to do so, for instance).
I doubt this issue is caused by amarok. Its symptoms are eerily similar to the well known ALSA issue where one application greedily hogs *hw:* instead of using default (PulseAudio is configured to do so, for instance).