After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674293 - [Gapless] Banshee ignores "stop when finished" and always repeats all once it reaches the end of an album
[Gapless] Banshee ignores "stop when finished" and always repeats all once it...
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Playback
2.4.x
Other Linux
: Normal major
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks: 638943
 
 
Reported: 2012-04-18 00:46 UTC by Damien
Modified: 2014-02-01 16:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Damien 2012-04-18 00:46:06 UTC
Basically summed up in the title. When I'm listening to a song and I select Playback->Stop When Finished, the next song still plays after the current one finishes. Also, when I'm listening to an album, instead of stopping playback once the last song is done, it restarts at the beginning.
Comment 1 Damien 2012-04-18 23:33:00 UTC
After doing some more testing, I've discovered that this only happens when gapless playback is enabled. Perhaps Banshee is prematurely fetching the next track without checking to see if playback should end after the current one.
Comment 2 Andrew Burrow 2012-10-16 05:11:20 UTC
Thanks! This bug has been driving me nuts.
Comment 3 Yves 2013-04-27 17:31:54 UTC
I have been experiencing the exact same issue, and indeed this would tend to drive someone nuts ~ Will try disabling the gapless playback option, but I'd be happy to help replicate the problem if there is interest in getting this fixed.
Comment 4 Martey Dodoo 2014-01-08 01:07:54 UTC
This sounds like this is a duplicate of bug #634798.
Comment 5 Andrés G. Aragoneses (IRC: knocte) 2014-02-01 16:57:25 UTC
I believed I fixed this with the fix for bug 679938.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.

(Fixed in master and the stable-2.6 branch, which means the fix will be in 2.9.1 and 2.6.2.)