Bug 13307 – SqueezeCenter can't resolve IP Addresses when configured for Autostart

Bug 13307 - SqueezeCenter can't resolve IP Addresses when configured for Autostart

Summary:

SqueezeCenter can't resolve IP Addresses when configured for Autostart

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Controller
Version:	7.3.4
Platform:	PC Windows XP

Importance:	-- minor with 1 vote (vote)
Target Milestone:	7.4.0
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-08-09 06:44 UTC by Paul W Panish
Modified:	2009-10-13 13:03 UTC (History)
CC List:	8 users (show)

See Also:
Category:	---

Attachments
SqueezeCenter Server Log (32.90 KB, text/plain) 2009-08-09 06:44 UTC, Paul W Panish	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 Paul W Panish 2009-08-09 06:44:58 UTC

Created attachment 5591 [details]
SqueezeCenter Server Log

When SqueezeCenter 7.3.4 is configured for autostart it's unable to resolve
external IP addresses after a reboot. Once a SqueezeCenter is stopped and
restarted it behaves properly.

This bug is a continuation of Bug 12475 which has been marked as resolved.
Unfortunately the fix was not valid for Windows systems (see forum for
continued proplem reports).

I'm running nightly build version 7.3.4-27864 using Windows XP SP3

Comment 1 Chris Owens 2009-08-17 09:07:39 UTC

Paul would you mind posting a link to the forum thread?  This is causing much confusion and discussion about what it might be.

Comment 2 BastiaanR 2009-10-01 02:18:10 UTC

Requested links to the forum:

1.   http://forums.slimdevices.com/showthread.php?t=68424
2.   http://forums.slimdevices.com/showthread.php?t=67211
3.   http://forums.slimdevices.com/showthread.php?t=64400

The last one is the long thread.

Comment 3 Paul W Panish 2009-10-07 06:01:36 UTC

This problem is no longer evident in release 7.4.0 - r28672. Since there was no mention of a solution to this problem in release notes or Bugzilla, I'm downgrading the bug to minor rather than marking it as resolved. It should be closed if there is no longer a need for investigation of cause. 

I will also post a message to the main forum thread.

Comment 4 James Richardson 2009-10-07 06:05:25 UTC

Andy: has anything changed with the release of 7.4.0 that would have resolved this issue?

Comment 5 Andy Grundman 2009-10-08 09:22:35 UTC

Yeah this should be fixed.