Summary: | Amarok doesn't continue playing playlist | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Tom Kijas <t.kijas> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | cycoone, kylepablo, matt.casters, sub |
Priority: | NOR | ||
Version: | 2.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tom Kijas
2009-06-10 21:43:48 UTC
I can confirm this issue, also on Kubuntu 9.04, amarok 2.1, KDE 4.2.90 (KDE 4.3. beta 2) Do you both use the Xine backend? Not a concision decision, but yes, I'm using the xine back-end. Confirmed then. I also experience this (Amarok 2.1.1, KDE 4.2.4, Xine Backend, QT 4.5.1, Gentoo) Also if I queue multiple tracks it stops after the first one. *** Bug 201128 has been marked as a duplicate of this bug. *** I had something happen yesterday that might shed a little bit of light on a situation where this happens. It is consistent and reproduceable. I have most of my collection on an external USB drive and it is checked in the list of folders as part of the collection. When my PC starts up, this drive is not automounted (I am doing a cleanup in my archive before moving this drive to a small server in our house). So I need to mount it before I can play from it. I do this by clicking on it in Dolphin. Yesterday I forgot to do this and started Amarok and clicked to play a few songs. Of course it did not play, so I went to Dolphin, clicked on the drive so it mounted and then went back to Amarok. The song I clicked on now played, but it stopped after playing only one song. Also, If I had a song playing and added another one to the playlist, Amarok would immediately jump to the new song and start playing it instead of just appending the new song to the list. Restarting Amarok fixes the problem. Amarok 2.1.1, Kubuntu 9.04, KDE 4.3 Oceanwatcher and my experience sound a lot like Bug 192114. That bug was made a duplicate of Bug 191199 which I'm not sure I agree with, but I think this bug and Bug 192114 are definitely the same thing. Sorry, must have mistyped the number in that other bug, corrected now. *** This bug has been marked as a duplicate of bug 192114 *** |