Version: 1.2.3 Debian/Unstable binary (using KDE KDE 3.3.2) Installed from: Debian testing/unstable Packages OS: Linux If I try to play something while the audio device is busy, the xine engine (which I use) gives an error, and this is fine. Though, instead of stopping playing, amarok tries to play the next track, and so on until it finishes the playlist. This way it loses the current position, increases the scores of all the tracks, and produces tons of error pop-ups. I think that if an output error occurs amarok should just stop on the current track.
This behaviour was changed. I think we're stopping now.
Same bug as 126660 and 121109
*** Bug 121109 has been marked as a duplicate of this bug. ***
*** Bug 126660 has been marked as a duplicate of this bug. ***
No, it sometimes stops, but not always, at least in 1.3.9 . Example 1: On KDE startup, arts keeps the sound card busy for a while. Amarok complains that it couldn't initialize the xine engine and stops playback Example 2: I am playing music with beep-media-player and press Play on Amarok. It stops playback correctly. Example 3: (Reproducible :() Another software (for example, it happens with Skype after a conversation, or with Google video after stopping the video) does not release the sound card. Amarok keeps skipping files, even causing the computer to half-hang - mouse is half-responsive, keyboard not at all. Example 3, worst case: I have both Skype and Amarok minimized to tray, I cannot kill them as I have no keyboard, the mouse generally works but right-clicking the tray icon does nothing. My computer is completely frozen :(
This appears to still be occurring in SVN.
This is definitely still a problem in 1.4.6 & xine. There's code in EngineController::play that's supposed to prevent such behaviour, but it only kicks in if xine_play returns an error, which doesn't happen -- xine posts an event instead.
Ok, reopening then. I think I've seen this behavior too, so I'll confirm.
The problem still exists in 1.4.9.1 (using KDE 3.5.7 "release 72.9" openSuSe 10.3).
Unfortunately, Amarok 1.4.x is no longer actively maintained, as all the focus is on Amarok 2.0. Feel free to report any bug you might come across in Amarok 2.0