| 2007-10-25 10:30:22 |
Sridhar Dhanapalan |
bug |
|
|
added bug |
| 2007-10-25 14:20:58 |
Sridhar Dhanapalan |
description |
Binary package hint: amarok
Amarok has an option titled "Resume playback on start". I would assume that this means that if I exit Amarok (or if it crashes) and then restart it, it would resume playing the same track, from the time position it was at before the closure/crash. If the track was paused, it should resume in a paused state.
Instead, it skips to the next track in the playlist, and starts playing from the beginning of that track. |
Binary package hint: amarok
Amarok has an option titled "Resume playback on start". I would assume that this means that if I exit Amarok (or if it crashes) and then restart it, it would resume playing the same track, from the time position it was at before the closure/crash. If the track was paused, it should resume in a paused state.
Instead, it skips to the next track in the playlist, and starts playing from the beginning of that track.
This has been a bug on at least Feisty and Gutsy. According to https://bugs.kde.org/show_bug.cgi?id=134545 this is not a problem upstream. |
|
| 2007-10-28 13:56:27 |
Sridhar Dhanapalan |
bug |
|
|
assigned to amarok |
| 2007-10-29 10:27:04 |
Bug Watch Updater |
amarok: status |
Unknown |
New |
|
| 2007-11-05 10:56:26 |
Bug Watch Updater |
amarok: status |
New |
Won't Fix |
|
| 2007-12-04 08:04:08 |
Bug Watch Updater |
amarok: status |
Won't Fix |
New |
|
| 2007-12-04 23:05:28 |
Sridhar Dhanapalan |
description |
Binary package hint: amarok
Amarok has an option titled "Resume playback on start". I would assume that this means that if I exit Amarok (or if it crashes) and then restart it, it would resume playing the same track, from the time position it was at before the closure/crash. If the track was paused, it should resume in a paused state.
Instead, it skips to the next track in the playlist, and starts playing from the beginning of that track.
This has been a bug on at least Feisty and Gutsy. According to https://bugs.kde.org/show_bug.cgi?id=134545 this is not a problem upstream. |
Binary package hint: amarok
Amarok has an option titled "Resume playback on start". I would assume that this means that if I exit Amarok (or if it crashes) and then restart it, it would resume playing the same track, from the time position it was at before the closure/crash. If the track was paused, it should resume in a paused state.
Instead, it skips to the next track in the playlist, and starts playing from the beginning of that track.
This has been a bug on at least Feisty and Gutsy. According to https://bugs.kde.org/show_bug.cgi?id=134545 this is not a problem upstream.
There is an ongoing discussion about this at http://bugs.kde.org/show_bug.cgi?id=151466 |
|
| 2008-03-13 12:29:55 |
Parthan SR |
amarok: status |
New |
Incomplete |
|
| 2008-03-13 12:35:14 |
Parthan SR |
amarok: status |
Incomplete |
Invalid |
|
| 2008-03-13 13:23:59 |
Sridhar Dhanapalan |
amarok: status |
Invalid |
New |
|
| 2008-06-17 18:42:40 |
Bug Watch Updater |
amarok: status |
New |
Confirmed |
|
| 2008-07-12 14:23:13 |
Bug Watch Updater |
amarok: status |
Confirmed |
Invalid |
|
| 2008-07-13 13:33:19 |
Bug Watch Updater |
amarok: status |
Invalid |
Won't Fix |
|
| 2009-03-14 12:28:52 |
Jonathan Thomas |
amarok: status |
New |
Fix Released |
|
| 2009-03-14 12:28:52 |
Jonathan Thomas |
amarok: statusexplanation |
I just tested again in Gutsy. The inconsistency remains: sometimes it will skip to the next track on restart, and other times it will resume from where it left off. If Amarok was paused when it was closed, it still does not resume in a paused state. This means that I can't keep Amarok as part of my login session, as it starts playing immediately after I log in. |
It seems to work without skipping to the next track here in Amarok 2.0.2. And since upstream has said that they won't implement restoring as paused I'm closing this bug. |
|
| 2011-02-03 21:47:26 |
Bug Watch Updater |
amarok: importance |
Unknown |
Medium |
|
