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 654004 - [gapless] Banshee does not increase play count with repeat single
[gapless] Banshee does not increase play count with repeat single
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: general
2.0.0
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
: 656495 (view as bug list)
Depends on:
Blocks: 638943
 
 
Reported: 2011-07-05 12:55 UTC by terri.bugs
Modified: 2020-03-17 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description terri.bugs 2011-07-05 12:55:00 UTC 
Play count increases by +1 each time Banshee finishes a song and moves to a new song, but if repeat single is enabled play count is not increased until repeat single is removed and new (different) song begins. Then the play count is increased by +1 even if the song has been repeated several times. This bug can be reproduced every time with Banshee 2.0.0.
Comment 1 Michael Martin-Smucker 2011-07-05 13:02:07 UTC 
Thanks for reporting this! Do you have gapless playback enabled? And if you disable it in Edit > Preferences, can you still reproduce the bug?
Comment 2 terri.bugs 2011-07-09 17:16:32 UTC 
I had gapless playback enabled earlier, without it Banshee increases play count as it should with repeat single or repeat all (with only one item in the playlist). Curiously, with gapless playback enabled, the repeat all option still increases the play count even if playlist only includes a single item whereas repeat single does not.
Comment 3 Michael Martin-Smucker 2011-07-21 15:55:56 UTC 
Thanks for following up. I'm getting rid of the NEEDINFO status.
Comment 4 Michael Martin-Smucker 2011-08-18 15:03:00 UTC 
*** Bug 656495 has been marked as a duplicate of this bug. ***
Comment 5 Dr. Martin Senftleben 2011-08-18 15:47:30 UTC 
Oops, I didn't find this one. I have observed the same problem.
Why is it still on unconfirmed? Doesn't it happen elsewhere?
Comment 6 Michael Martin-Smucker 2011-08-18 15:58:46 UTC 
(In reply to comment #5)
> Oops, I didn't find this one. I have observed the same problem.
> Why is it still on unconfirmed? Doesn't it happen elsewhere?

No problem. As far as I know, the difference between UNCONFIRMED and NEW isn't particularly important to developers, but since we now have multiple reports of this, it's probably safe to confirm it.
Comment 7 André Klapper 2020-03-17 09:22:25 UTC 
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.