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 623676 - Incoherent behavior of next (shuffle) button
Incoherent behavior of next (shuffle) button
Status: RESOLVED DUPLICATE of bug 608781
Product: banshee
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-07-06 12:49 UTC by Nicolò Chieffo
Modified: 2010-07-17 13:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicolò Chieffo 2010-07-06 12:49:21 UTC
There's an incoherent behavior of "shuffle by" mode:
- The next (when shuffle is active) button always does "shuffle by song"
- Instead when a song ends and the next one must be picked, the selected "shuffle by" value is used
Comment 1 Gabriel Burt 2010-07-13 19:20:03 UTC
I don't understand.  In 'by album' mode, hitting next works fine for me, not for you?

I don't understand your second point at all.
Comment 2 Michael Martin-Smucker 2010-07-14 00:11:36 UTC
Perhaps this is a duplicate of Bug 608778?
Comment 3 Nicolò Chieffo 2010-07-17 08:35:30 UTC
maybe a dup.

But for sure when tou select shuffle by artist, and click on the next button a new artist is picked (as when suffle by song is selected).
On the other side if I don't use the next button, and I wait till the song end, shuffle by artist work
Comment 4 Michael Martin-Smucker 2010-07-17 13:41:53 UTC
Ahh, in that case, this sounds like a dupe of Bug 608781, and I'm going to mark it as such.

That bug is marked as WONTFIX because the current behavior is, in fact, intended.  The shuffle by artist/album modes treat entire artists or albums as a group, and if you press the skip button, you are effectively skipping the entire group of songs.  See 608781 for more details and discussion.

*** This bug has been marked as a duplicate of bug 608781 ***