Bug 15305 - backlight comes on while off with "Screen off" as screensaver
: backlight comes on while off with "Screen off" as screensaver
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: Screensavers
: 7.5.0
: All Other
: -- normal (vote)
: 7.5.0
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-14 18:47 UTC by Peter Watkins
Modified: 2010-04-08 17:25 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 Peter Watkins 2009-12-14 18:47:55 UTC
PB2 currently at 7.5.0 r8212, using MySB.com. My When off screensaver is "Screen off". The screen always goes completely dark when I turn the player off with the onscreen power button on the home screen. But usually within several hours the screen goes to "black but on" -- nothing on the display, but a very dim backlight, as for an LED screen that is on and attempting to display an all-black fullscreen image. 

This has been the case for a while now (several weeks at least). Sorry for not reporting it sooner.
Comment 1 Peter Watkins 2009-12-14 19:47:41 UTC
I don't know when the screen last "lit up" when off, but /var/log/messages has many sets of lines like these

Dec 14 16:20:16 squeezeplay: INFO   net.comet - Comet.lua:627 Comet {oldbox}: _handshake error: HTTP/1.1 401 Unauthorized
Dec 14 16:20:16 squeezeplay: INFO   net.comet - Comet.lua:997 Comet {oldbox}: handleAdvice state=CONNECTING
Dec 14 16:20:16 squeezeplay: INFO   squeezebox.server - SlimServer.lua:745 failed auth. Count: 15909 server: SlimServer {newbox} state: disconnected
Dec 14 16:20:16 squeezeplay: INFO   squeezebox.server - SlimServer.lua:745 failed auth. Count: 4365 server: SlimServer {oldbox} state: connecting
Dec 14 16:20:16 squeezeplay: INFO   squeezebox.server - SlimServer.lua:714 disconnected oldbox idleTimeoutTriggered: nil
Dec 14 16:20:16 squeezeplay: INFO   net.comet - Comet.lua:1038 Comet {oldbox}: advice is retry, connect in 4.83 seconds

oldbox is my production server, running 7.3.4, which fab4 should not attempt to connect to (see bug 14789). newbox is my development system which sometimes runs SVN 7.5.0 trunk.

Perhaps at some point my fab4 is giving up on MySB.com and trying to fall back to a local server, and that's triggering the problem?
Comment 2 Michael Herger 2009-12-14 22:56:35 UTC
I think I've seen similar behaviour when the update screen was popped while the device was powered off. Does this sound familiar?
Comment 3 Peter Watkins 2009-12-15 15:29:51 UTC
No, I'm afraid not. It happened again last night / today -- got home from work and the backlight is on. No announcement of a software update, and Settings > Advanced > Software only offers "Cancel".

I'll see if I can dig up a spare SD card to capture more from syslog.
Comment 4 Michael Herger 2009-12-15 21:38:35 UTC
Peter - there was a bad firmware being pushed out yesterday (one based on 7.4 code). Please update to 8224 and report back. Thanks!
Comment 5 Peter Watkins 2009-12-15 21:54:18 UTC
OK, I'm on 8224 now, and have manually tweaked syslog so I should get enough data (see bug 15311 -- even with the SD card, fab4 wasn't keeping more than about 1.5 hours of syslog messages). I'll keep you updated.
Comment 6 Peter Watkins 2009-12-17 19:08:01 UTC
Since updating to r8224, I got over 30 hours without seeing the problem, which is far better than I've seen in a while, so I think this may be fixed. 

I'll reopen if I see the problem again.
Comment 7 Chris Owens 2010-04-08 17:25:22 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!