At risk of being too technical, Amarok itself doesn't play music. The current version actually calls another application (known as an "engine") to play the music -- and the music playing runs in another thread/process so that when the GUI lags, (which WILL happen due to stupidness in the way X is designed) your music doesn't skip. So, A) it takes time for the "quit" message to get from one application to another, and B) if there's a bug in the configuration of the engine, that would likely cause this behaviour. 30 seconds seems like a lot to me, but perhaps it's just me.
Does upgrading to the Amarok in Hardy or Intrepid fix the issue? Of course, if the whole "using an engine" is the cause of the bug, then you may want to help with testing of Amarok 2, which uses some new- fangled KDE 4 library to play sound instead. Oh... and for what it's worth, last I checked, XMMS is no longer being maintained, so if it breaks and there's a bug, there's nobody that can fix it. *shrugs* -- Amarok Takes 30 Seconds To Stop Playing Music After You Quit The Program https://bugs.launchpad.net/bugs/58537 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
