Version: 2.4.0 (using KDE 4.5.5) OS: Linux When I change the track progression for the playlist, it does not update the "next track" display. The player does behave as expected in terms of track progression, but does not reflect the change in track progression in its display. Reproducible: Always Steps to Reproduce: Change the track progression in any way -- from random to standard, or random tracks to random albums. Actual Results: Next track display does not change to reflect the different track progression. However, when the current song ends, it does follow the changed track progression setting -- i.e. if it is set to random, it does go to a random track instead of going to the (incorrect) track listed. Expected Results: Next track display updates to reflect the change in track progression settings. Before upgrading to 2.4.0, Amarok would always update the next track display if there were changes to the track progression. The exception, however, for this bug, is that it DOES update if you queue a track. Otherwise, the display will not update as expected when the track progression is changed.
Created attachment 56255 [details] Re-Connect navigator change connection was (probably accidently, since the disconnection is still present) lost in http://gitweb.kde.org/amarok.git/commitdiff/049daccfdf7255b1873d0983fdfcbff9446c2987 @Ralf: I assume this was just a maintainance update and there was no intention to remove that connection? (navigatorChanged() -> updatePrevAndNext()) Also: errr... link to current non-gitorious patch policy (review request? from here? - and more important, can i push with just my KDE git account?)
Hi Thomas: the policy to follow is now the following: 1. get an identity at http://identity.kde.org 2. submit the patch or code to http://git.reviewboard.kde.org Thank you :)
This is an automated message from the triager: Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug? Without feedback within a month we will close this bug as resolved. Thank you for your understanding.
I am no longer having this problem as of release 2.4.1. Thanks very much for the fix!