Summary: | Queue currently playing song doesn't work correctly when Random Tracks is on | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Harley Laue <losinggeneration> |
Component: | Playlist | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ashl1future, jonny.privateproperty, teo |
Priority: | NOR | ||
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Harley Laue
2009-05-27 18:20:05 UTC
I can confirm this behaviour in Suse 11.1 using 2.1 Cannot confirm it on Amarok 2.2-SVN Neither can I, seems solved in 2.2-SVN Queuing the currently playing track does not currently work in SVN. If it's queued it should repeat that song and then dequeue it. It doesn't dequeue it either, right clicking on the song after it's done and skipped playing it the second time the option is to dequeue it and not to queue it. To duplicate: 1) Turn on random tracks 2) Start playing a track in the playlist 3) Queue the track 4) When the track is finished it goes on to a different track (the bug) Yes. In this case, I confirm it. Yes, confirmed too, forgot to set the random mode previously. This seems to be fixed in current git, I can't reproduce. Perhaps comment #4 wasn't clear enough... So please follow these directions to reproduce the bug: 1) Turn on random tracks 2) Add two tracks to a playlist 3) Start playing a track in the playlist 4) Queue the track that is currently playing 5) When the track is finished it goes on to a different track (the bug) The correct behavior: 3) Start playing a track in the playlist 4) Queue the track that is currently playing 5) The currently playing track is played again Also, it currently removes the queue'd icon from the track, but if you right click the track that was supposed to be played, it gives the option to dequeue it. This indicates that its queue possition is being deincremented (to zero) but it's still considered queued. I hope this clears up any confusion about how to reproduce this bug. True, this is still not fixed here, git build of 2 minutes ago. Oops! I must have misunderstood the directions then. I'll take a closer look. Ok, I can confirm this and I have also discovered other weird Random navigator behaviour, not only with queuing. commit 4ed45244987b2b52dfe23b4445c5b6c18a3caec5 Author: Teo Mrnjavac <teo@getamarok.com> Date: Tue Sep 1 17:24:28 2009 +0200 Correctly handle queuing in the RandomTrackNavigator. BUG: 194328 |