Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 70858

Summary:	xmms does not save options or state
Product:	[Retired] Red Hat Raw Hide	Reporter:	Gary Peck <gbpeck>
Component:	xmms	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-08-08 21:25:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gary Peck 2002-08-06 05:51:18 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/0

Description of problem:
When I change any of xmms' options or change its state (e.g. toggle shuffle
mode), exit xmms, and then start it again, the option/state reverts back to its
old value. This includes options in the "Options" tab of xmms, switching skins,
toggling shuffle mode, toggling the  windowshade status of a window, and the
position in the playlist.

If I look in .xmms/config after exiting xmms, the old value is still in there.
If I then edit .xmms/config manually and restart xmms, it sees the new value.

Version-Release number of selected component (if applicable):
xmms-1.2.7-9

How reproducible:
Always

Steps to Reproduce:
1. Start xmms
2. Toggle shuffle mode on
3. Exit xmms (by clicking on the X in the corner)
4. Start xmms again


Actual Results:  Shuffle mode was turned off.

Expected Results:  Shuffle mode should have been on.

Additional info:

Comment 1 Gary Peck 2002-08-08 21:25:23 UTC

Never mind. I thought the bug was a result of upgrading to rawhide xmms, but it
turns out to be an interaction between xmms and a plugin I installed at around
the same time. Removing the plugin fixed the problem. Will follow it up with the
xmms developers.

I'm going to change the bug state to NEEDINFO, or should it be CLOSED?