Bug 12079 – Unable to access SqueezeCenter using Safari on remote Mac

Bug 12079 - Unable to access SqueezeCenter using Safari on remote Mac

Summary:

Unable to access SqueezeCenter using Safari on remote Mac

Status:	CLOSED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	7.3.2
Platform:	Macintosh MacOS X 10.5

Importance:	P3 normal (vote)
Target Milestone:	8.0.0
Assigned To:	Spies Steven

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-05-16 15:32 UTC by Michael Robinson
Modified:	2012-02-27 17:33 UTC (History)
CC List:	0 users

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 Michael Robinson 2009-05-16 15:32:35 UTC

This problem has occurred after upgrading to OS X 10.5.7 and Safari 3.2.3  from OSX. 10.5.6 and previous version of Safari.

I have an iMac and Mac Book Pro, both on private IP addresses.  The iMac is running SqueezeCenter and I usually access the SqueezeCenter browser interface using Safari on the Mac Book Pro.

Since upgrading the iMac and Mac Book Pro to the OSX 10.5.7, I can no longer access the SqueezeCenter browser interface using Safari on the Mac Book Pro.

On Safari, I get the following error: "Slow Script A script on the page "SqueezeCenter" (http://10.0.1.111:9000/) is making Safari unresponsive. Do you want to continue running the script, or stop it? Stop Continue"

Pressing "Continue" produces the error again.

Pressing "Stop" leaves the browser page saying "Loading SqueezeCenter" but it does not progress beyond this.

I can successfully access the SqueezeCenter browser interface using Safari on the iMac (local access)

I can successfully access the SqueezeCenter browser interface using Firefox on the Mac Book Pro (remote access)

Comment 1 James Richardson 2009-05-18 09:22:23 UTC

QA will investigate this one

Comment 2 Spies Steven 2009-07-30 10:54:52 UTC

Michael, since SqueezeCenter 7.3.3 and Safari 4.0.2 has been released do you still see this issue?  I was never able to reproduce myself.

Comment 3 Michael Robinson 2009-08-01 07:08:30 UTC

I'm now running Safari 4.0.2 and SqueezeCenter 7.3.3  and haven't seen the issue any more.

Comment 4 Spies Steven 2009-08-03 11:41:35 UTC

Thanks for the feedback Michael!  Closing as works for me.

Comment 5 James Richardson 2012-02-27 17:33:37 UTC

Closing resolved bugs - if you feel this bug still exists please first re-test
with the latest SW/FW version.  If you are able to reproduce then feel free to
reopen and attach new logs / steps to reproduce.