Hide Forgot
Description of problem: I am subscribed to some podcasts and I have added some of the podcasts to the playing lists. If I click on pause button and then resume the playing, the podcast starts from the beginning, rather than from the point it was. Version-Release number of selected component (if applicable): amarok-libs-2.4.3-1.fc16.i686 amarok-2.4.3-1.fc16.i686 amarok-utils-2.4.3-1.fc16.i686 How reproducible: Always Steps to Reproduce: 1. Add the following podcast to the Local Podcast list: http://downloads.bbc.co.uk/podcasts/worldservice/how2/rss.xml 2. Select several episodes and add the to the playing list 3. Start playing (I have it in random mode) 4. Press the pause button 5. Resume playing Actual results: The current episode starts from the beginning, rather than the point when I pressed pause.
Please retest with latest versions of amarok/phonon, https://admin.fedoraproject.org/updates/FEDORA-2011-17355/amarok-2.5.0-1.fc16 in particular.
Testing the aforementioned bbc podcast feed with amarok-2.5.0 seems to work fine for me. I listed to the first 30 seconds, paused for a minute or so... and resuming picks up where it left off.
Hi, you are right, just using the steps I pointed out the bug is not shown. Here is a rather more complex sequence of events that can help you to reproduce the bug: 1. Add the following podcast to the Local Podcast list: http://downloads.bbc.co.uk/podcasts/worldservice/how2/rss.xml 2. Add the whole list of podcast to the playing list 3. Start playing (I have it in random mode) 4. Pause the first episode and resume (that works) 5. Pause the first episode and resume (that works as well) 6. Suspend the computer, for instance just closing the computer lid 7. Open the lid again and the current episode continues just fine 8. When the current finishes, the playlist is strangely stopped (maybe that's other bug). Then I press "Next song" and the playlist resumes. 9. Now press the pause button and the current episode starts from the beginning (the current bug). I was also able to reproduce the bug with this sequence of events: 1. Add the following podcast to the Local Podcast list: http://downloads.bbc.co.uk/podcasts/worldservice/how2/rss.xml 2. Add the whole list of podcast to the playing list 3. Start playing (I have it in random mode) 4. Exit amarok with Ctrl-Q 5. Open amarok again, the playlist is resumed. 6. When the current episode finishes, the playlist is strangely stopped (maybe that's other bug). Then I press "Next song" and the playlist resumes. 7. Now press the pause button and the current episode starts from the beginning (the current bug). I hope that this helps to nail down the issue. Regards, Enrique
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.