Bug 221588 - Amarok does not reset "Stop after current" mode of operation until restarted.
Summary: Amarok does not reset "Stop after current" mode of operation until restarted.
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (show other bugs)
Version: 2.2.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 2.3.0
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-06 23:37 UTC by GGG
Modified: 2010-02-07 12:53 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GGG 2010-01-06 23:37:11 UTC
Version:            (using KDE 4.3.3)
OS:                Linux
Installed from:    Ubuntu Packages

I am using Amarok 2.2.1 as part of KDE 4.3.3 on Ubuntu 9.10 x86_64.

In playlist I choose to "Stop after current" for some song. When it has played the jumping to the next track does not happen, which is what is expected. But, when I manually start playing another track, it gets fully played and then the player stops as the curent track was the last to be played when it is not (no "Stop after current" sign is present at playlist at all!) After exiting/killing amarok and starting it over works OK - one track is being played after another until manually stopped.

To reproduce: start Amarok, populate the playlist, turn random playing/cycle playing off (so the playlist is in normal operation now), mark certain track as "Stop after current". Start playing the tracks. When the selection reaches the marked one, the playback is stopped. Then manually start playing of an arbitrary track. It is completely played but then the playback is stopped while is shouldn't - it should go to the  next track.
Comment 1 Kostya Sha 2010-02-07 03:31:58 UTC
Could you try to reproduce it on 2.2.2 ?
Comment 2 Myriam Schweingruber 2010-02-07 04:00:36 UTC
Changing status
Comment 3 GGG 2010-02-07 12:53:14 UTC
I've checked 2.2.2 - the problem doesn't seem to exist. Thanks to all, closing this one.