Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 188603 - Patch to fix playlist randomize
Patch to fix playlist randomize
Product: Fedora
Classification: Fedora
Component: xmms (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2006-04-11 13:28 EDT by David Cantrell
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 1.2.10-29
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-06 16:20:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
xmms randomize fix (1.42 KB, patch)
2006-04-11 13:28 EDT, David Cantrell
no flags Details | Diff

  None (edit)
Description David Cantrell 2006-04-11 13:28:47 EDT
Well known problem.  XMMS sucks at randomizing large playlists.  Attached is a
patch from David Shea of the more-or-less dormant Peachtree Linux project.  It
corrects the randomization problem in xmms so it doesn't cycle through the same
4 or 5 songs.
Comment 1 David Cantrell 2006-04-11 13:28:47 EDT
Created attachment 127625 [details]
xmms randomize fix
Comment 2 Ville Skyttä 2006-10-04 14:03:24 EDT
Reassigning to current xmms maintainer (myself - haven't seen this bug report 
before now).
Comment 3 Ville Skyttä 2006-10-19 16:48:14 EDT
Upstream CVS appears to have similar changes, see 
http://cvs.xmms.org/cvsweb.cgi/xmms/xmms/playlist.c.diff?r1=1.88&r2=1.89 and 
the last hunk of 

Could you check if they work for you?
Comment 4 David Cantrell 2006-10-23 11:32:41 EDT
I've long since stopped using xmms in Fedora now, but looking at the upstream
code, it appears that they've finally fixed that problem.
Comment 5 Ville Skyttä 2006-11-06 16:20:08 EST
Upstream changes applied in 1.2.10-29.fc*

Note You need to log in before you can comment on or make changes to this bug.