Version: 2.0.1 (using KDE 4.2.1) OS: Linux Installed from: Unlisted Binary Package Possibly related to bugs 171754, 172372, 186172, and maybe even 180339. For some tracks (VBR maybe?) in my collection, Amarok will stop playing after the current track finishes and does not skip to the next one. One track, for example shows the following after it stops: Total track time (in playlist): 2:52 Time Elapsed: 2:51 Time remaining: 0:01 So the track stops one second short of when Amarok expects it to. I guess that Amarok is expecting the timer to reach zero before it counts a track as finished, but that is obviously not happening. I am using the xine backend. Can I suggest that Amarok includes some defensive programming to routinely check whether the track is actually playing? Surely that is possible to do, even if this is technically a fault of the backend (gstreamer or xine, or both) not reporting the correct track length. I am raising this bug as new against Amarok because the other ones I have referenced above have been pushed over to the backends. I think that Amarok should have a guard against this behaviour included in its code nonetheless. If I had more time on my hands I might have attempted a patch myself, but that isn't possible right now I'm afraid.
One other thing to note, is that the OSD pops up just as the track finishes playing showing the same track again. So the program obviously is aware that it finished playing it, but confused enough that it won't advance to the next one.
Please check for dupes before making bug reports. *** This bug has been marked as a duplicate of bug 180339 ***
You mean the bug that I referenced in my report above? No, I don't believe it is not a duplicate of that because: 1. I am playing local files, not internet radio 2. Amarok does not end up in a frozen state. I can play the next track if I start it manually. It just does not change tracks automatically in a playlist. Have I missed anything? Otherwise would like this bug reopened. Thanks
I have a little more information: It started just after I used "Stop playing after track" for the first time, but it is possible that my computer also hardlocked and had to be reset around the same time (unrelated issue). From then on, it seems that Amarok thought that the "Stop playing after track" setting was on for all tracks! Even deleting ~/.kde4/share/apps/amarok/ and rebuilding my collection didn't fix it. However, what did fix it was changing the playlist setting to random:tracks. Afterwards I could turn random off again and it now works ok. Annoyingly I cannot reproduce this any more since it started working again. Has anyone else has seen the same behaviour? I'll leave this bug open as open/UNCONFIRMED for a while unless I can't reproduce it again, in which case I'll close it myself.
I can't reproduce this anymore with SVN trunk. Probably fixed.
Yeah I can't get it to behave like that any more either, even with the same version. In fact I was going to close this bug soon but you saved me the trouble!