Bug 14018 - Long Power OFF doesn't work if Baby is off and Flickr screensaver is displayed
: Long Power OFF doesn't work if Baby is off and Flickr screensaver is displayed
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Screensavers
: Include FW version in comment
: PC Windows XP
: P1 normal (vote)
: 7.4.0
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-13 19:58 UTC by Mickey Gee
Modified: 2009-10-05 14:37 UTC (History)
6 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2009-09-13 19:58:09 UTC
I have a battery-only Baby with r7541 firmware set to display Flickr My Photos when the unit is turned OFF. When I turn off my unit with a short press of the Power button, the Flickr screensaver starts up. Immediately afterwards, when I hold down the Power button longer to completely turn off Baby, the unit does not turn off.

If I depress the Power button quickly, the Baby turns on. I can then hold down the Power button longer to completely turn off Baby.

Happens if battery-only or AC Baby.
Comment 1 SVN Bot 2009-09-14 14:03:12 UTC
 == Auto-comment from SVN commit #7560 to the jive repo by richard ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7560 ==

Fixed bug #14018
You could not shutdown (long power off) when a screensaver was active.
Comment 2 James Richardson 2009-10-05 14:37:05 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.