Bug 251844 - impossible to go back in playlist with global keys if album-random-mode is enabled
Summary: impossible to go back in playlist with global keys if album-random-mode is en...
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Shortcuts (show other bugs)
Version: 2.3.2
Platform: Debian unstable Linux
: NOR normal
Target Milestone: 2.4.0
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-20 20:11 UTC by Modestas Vainius
Modified: 2013-08-18 13:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Modestas Vainius 2010-09-20 20:11:30 UTC 
Version:           2.3.2 (using KDE 4.4.5) 
OS:                Linux

I'm forwarding this bug from Debian BTS. Even if original reporter reported it against 1.4.10, I have confirmed it on 2.3.2!

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517717
--------------------------------------------------------
It is impossible to use the globalkeys to go back in playlist if album-random-mode is
enabled. Instead the same song starts again. It is no problem to go forward
in playlist in this mode. And it is no problem to go back if the
normal-random-mode is enabled. It is also possible to go back in playlist
with album-random-mode with the GUI-buttons.


Reproducible: Always
Comment 1 Myriam Schweingruber 2011-06-04 12:10:43 UTC 
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.
Comment 2 Myriam Schweingruber 2011-07-16 07:41:33 UTC 
Closing for lack of feedback. Feel free to reopen if you can still reproduce
this with Amarok 2.4.2 beta 1 or later and provide the necessary feedback.
Comment 3 Modestas Vainius 2013-08-18 13:18:18 UTC 
Note sure when it was fixed but it works in 2.8.0 (at least).