Bug 11097 - Clock screensavers should not engage if system clock hasn't been set.
: Clock screensavers should not engage if system clock hasn't been set.
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: Screensavers
: unspecified
: PC Other
: -- normal (vote)
: 7.4.0
Assigned To: Ben Klaas
: CAT
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-15 17:01 UTC by Blackketter Dean
Modified: 2009-10-05 14:34 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2009-02-15 17:01:01 UTC

    
Comment 1 Blackketter Dean 2009-04-14 13:46:35 UTC
*** Bug 11794 has been marked as a duplicate of this bug. ***
Comment 2 James Richardson 2009-04-14 15:06:51 UTC
CAT PR-0093

When the Fab4 is powered on, and no server is available, the Date/Time screen
saver will Reverted to Jan 1 1970 00:01.
---------------------
Since we KNOW that no server is available, how about we display a message with
Help Text letting the customer know there is something wrong with the
connection?

We should suppress the 'screen saver' display a message for xx minutes, then
power off the display like we do for all the other Players that do not have a
RTC
Comment 3 Ben Klaas 2009-06-09 15:05:20 UTC
fixed r6049

clocks can be previewed from settings menu, but if clock is not set to a year of at least 2009, clock screensaver will not engage
Comment 4 James Richardson 2009-10-05 14:34:39 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.