Bug 5567 – Can't save interface changes for Server Settings

Bug 5567 - Can't save interface changes for Server Settings

Summary:

Can't save interface changes for Server Settings

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	6.5.4
Platform:	Other Fedora

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-09-25 10:35 UTC by Kent Knudsen
Modified:	2009-01-29 09:47 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Kent Knudsen 2007-09-25 10:35:20 UTC

At every start of SlimServer the interface in the webbrowser is set to Light. This problem started after upgrade from 6.5.3 to 6.5.4

Comment 1 Chris Owens 2007-11-01 10:35:11 UTC

Support to contact this user.

Comment 2 Chris Owens 2007-11-01 10:46:49 UTC

Possibly related to bug 5621

Comment 3 KDF 2007-11-01 21:14:21 UTC

it seems unlikeyly to be related.  skin choice is a pref, or a url override.  The selected player is a cookie (which the skin resets if the player is missing or later coming back online after server restart).  Bug 5621 is a cookie problem, while the interface seems to be another thing.  We would need more info.  What url is used, what is the pref in the prefs file when trying to change the setting, etc.

Comment 4 Dan Evans 2007-11-05 12:27:13 UTC

I had the user run some tests with deleting his conf file and starting anew.  He wrote:

"I wanted to test the skin-change and web-interface on a totally new device by adding its IP as allowed in the security settings. It was at this point I discovered the IP address wasn't written to the conf-file, so I investigated the permissions on the file.  The file slimserver.conf wasn't written to since around the day I upgraded (25/9), root was owner and groupowner. The file was a backup from my prior installation and that way it got root as owner.

I changed the permissions so now slimserver is both owner and groupowner. That did the trick."

So, bug will be closed as WORKSFORME.