Bugzilla – Bug 10810
Squeezebox Controller will prevent computer from going into Standby
Last modified: 2009-09-15 18:31:25 UTC
Customer states that when he turns his SB3 off, his computer will not go into Standby because the SB3 will constantly ping for SqueezeCenter..even when the SB3 is off. Customer is on an XP machine. This is what the customer wrote in with. After installing latest squeezecenter software my system will get woken up the minute it goes into standby. If I uninstall squeezecenter software my system will stay in standby. I have wake on LAN enabled, and it appears that the player is pinging my server. if I unplug the network cable to my wireless router, or unplug the squeezebox then the system will not get awoken the minut it goes into standby. I unchecked the "prevent system from going into standby" in the plugin's, but that didn't make a difference. Withe the old software the system would sometimes go into standby while playing but it wasn't a problem. 7.3.2
Verified, SqueezeCenter 7.3.1 & 7.3.2(3) are preventing Windows (XP/Vista) from going to S3 When SC is shutdown, the system is able to enter S3 (Standby) with no problems. When SC is running, the system attempts to go to S3, but is woken immediately. This will happen with or with out players (IP3k/SqueezeOS) attached. ----- When SC is running as a Service, the same issue occurs. ========================================== |SC 7.3.2(3) MAC does not have this issue| ========================================== =================================== SC 7.3.0 does NOT have this problem MAC does NOT have this issue ===================================
Steven theorizes that players on the same network may be causing this behavior, regardless of the fact that they're not connected. Related to bug 10804.
Steven will investigate further
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
For some reason Bugzilla did not change the target when I did this yesterday. Or maybe it was me. In either case, I'm trying it again.
This is supposedly no longer an issue in 7.4, need to be verified.
*** Bug 13349 has been marked as a duplicate of this bug. ***
This appears to be fixed in 7.4 Please re-test with that version, if there is still and error, reopen and add more details.