Bug 11263 – Unable to access some Settings areas in SqueezeCenter

Bug 11263 - Unable to access some Settings areas in SqueezeCenter

Summary:

Unable to access some Settings areas in SqueezeCenter

Status:	RESOLVED INVALID

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	7.3.2
Platform:	PC Windows XP

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-05 12:57 UTC by Julius Dauz
Modified:	2009-03-20 14:46 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Sever log (1.78 KB, application/octet-stream) 2009-03-05 12:57 UTC, Julius Dauz	Details
View All 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 Julius Dauz 2009-03-05 12:57:01 UTC

Customer running SC 7.3.2 and has tried 7.4. Same exact issue with both versions

In default skin he is unable to access the following Settings pages, it just hangs. And in Classic Skin when he attempts to access the same pages, he gets a page load error.

Settings > Player tab > Audio

Settings > Advanced tab > Network

Settings > Advanced tab > File Types

We've tried clean install, multiple browsers, clearing browser cache/ resetting browser settings to no avail.

Comment 1 Julius Dauz 2009-03-05 12:57:31 UTC

Created attachment 4887 [details]
Sever log

Comment 2 Julius Dauz 2009-03-05 13:01:44 UTC

Note: Aside from the three mentioned Settings pages, SqueezeCenter works normally.

Comment 3 Michael Herger 2009-03-06 02:05:37 UTC

All the pages you mention are using the S::U::Misc::findBin functions which calls File::Which. The line the log is complaining about is checking a file path in a regex which _might_ be unsafe. We therefore need to know what path or filename is being checked in those cases.

Please set os.paths=debug (Settings/Advanced/Logging) and try to open one of those pages. Do you see something new in the server.log?

Comment 4 Julius Dauz 2009-03-09 13:56:09 UTC

Michael,

This customer responded to me over the weekend and by wiping his machine and reinstalling Windows, he fixed the issue. I think its safe to say the issue was on the user's end and this bug can be closed for now. 

He is in the process of reinstalling all his other applications now so if anything he installs causes this issue, he will let me know.