Bug 14582 - My screen saver doesn't turn on since I upgraded to the new FIrmware on my Duet
: My screen saver doesn't turn on since I upgraded to the new FIrmware on my Duet
Status: CLOSED WORKSFORME
Product: SB Controller
Classification: Unclassified
Component: Screensavers
: unspecified
: PC Windows Vista
: -- normal (vote)
: Investigating
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-05 06:13 UTC by Alex
Modified: 2012-02-27 17:18 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2009-10-05 06:13:17 UTC
Hello,

I upgraded to the new Squeezebox firmware yesterday (awesome by the way ;-) ) but since then, the screensaver never appears on my Duet controller. I've checked the settings, defined a delay of 10 seconds, chose the digital clock and said I wanted it to appear when not playing, but nothing happens. The controller stays on the screen I was on. 

Cheers

Alex
Comment 1 James Richardson 2009-10-05 07:59:33 UTC
Alex: please power cycle your Controller.  Also, are you testing this in our out of the cradle?
Comment 2 Alex 2009-10-05 08:25:56 UTC
(In reply to comment #1)
> Alex: please power cycle your Controller.  Also, are you testing this in our
> out of the cradle?

Hi

I tried both in an out. And the screensaver didn't appear even after several minutes.

What do you mean by Power Cycle?

Greetings for Logitech Europe Offices
Thanks for your help
Alex
Comment 3 James Richardson 2009-10-05 08:37:59 UTC
press and hold the power button until the unit turns off
then remove the battery
then put the battery back in
then press and hold the power button until the unit turns on

Also, does the same thing happen with other SS or just that one
Comment 4 James Richardson 2009-10-06 16:05:19 UTC
Alex: any update? have you been able to verify if other SS have the same issue?
Comment 5 James Richardson 2012-02-27 17:18:53 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.