Bug 227122 - Amarok plays previous song again after a track is queued
Summary: Amarok plays previous song again after a track is queued
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (show other bugs)
Version: 2.2.90
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 04:04 UTC by E.T. Anderson
Modified: 2010-03-15 19:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description E.T. Anderson 2010-02-16 04:04:05 UTC
Version:           2.2.2.90 (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

I have my playlist set on random shuffle and repeat playlist.
When I queue a track to play next (instead of allowing the random selection) the queued song will play and the next "random" pick will be the song that played just before the one I queued. Even as I write this, it sounds confusing, so here's a try at a timeline representation:

Song A playing > I queue song B > song B plays > song A plays again > random selection resumes.

I would expect the queued song to play and then the list revert to random, and certainly it's weird to have the repeat. This is with Amarok version 2.2.2.90 (2.3 beta).
Comment 1 Myriam Schweingruber 2010-02-21 17:05:00 UTC

*** This bug has been marked as a duplicate of bug 222503 ***
Comment 2 bob5972 2010-03-12 07:14:38 UTC
This has nothing to do with bug 222503 (which is a krunner bug with non-ascii characters?).  If it's a duplicate of something else, I couldn't find it.

I can confirm that this same problem with the Gentoo package of amarok-2.2.2.90.  Queueing a song while something else is playing, will cause the playing song to repeat after the queue is emptied.
Comment 3 Myriam Schweingruber 2010-03-15 19:20:52 UTC
Yes, wrong bug number from me, sorry. For some strange reason this mail only ended up in my inbox today, sorry for the noise.

This has been recently fixed in current git IIRC, so expect this to be solved in 2.3.1