Version: 1.4.4 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux When amarok tries to submit track to last.fm and the connection speed is not fast, so timeout occurs. After it the amarok just stops playing anything and it is unavailable to control its window besides using xkill or smth like that.
I can confirm that this bug exists on 1.4.4 under Debian etch amd64. It happens exactly as described above. This means that amarok is unusable for anyone who wants to use last.fm. I started with a clean ~/.kde/share/config/amarokrc and added all of the appropriate configuration from scratch and reproduced this. If i turn off last.fm track submission, amarok works reliably.
I've managed to work around this bug by setting the proxy settings in kcontrol to use the system settings (from the http_proxy environment variable). I'm a GNOME user except for a couple of KDE's killer apps (amarok & K3B, to be specific), so it didn't occur to me that amarok might be using a different proxy setting for its engine and its track submission, and that i needed to find where else it might be set. Regardless, this is clearly a bug in amarok: it shouldn't hang if it hasn't got network connectivity to last.fm, but should instead queue the tracks up like xmms-scrobbler does.
I can confirm the bug too. It can be reproduced on amarok 1.4.4, 1.4.5 and 1.4.6. I'm using Debian Testing/Unstable, KDE 3.5.7.
Same on Kubuntu 7.04 KDE 3.5.7 amarok 1.4.6
this is fixed in amarok 2 (afaict)