Bug 15654 - Black screen immediately after setup
: Black screen immediately after setup
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: Setup
: 7.5.0
: PC Windows XP
: P1 normal (vote)
: 7.5.0
Assigned To: Ben Klaas
: CAT
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-07 23:02 UTC by Mickey Gee
Modified: 2010-04-08 17:26 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments
full log from during factory reset (53.97 KB, text/plain)
2010-02-08 08:03 UTC, Michael Herger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2010-02-07 23:02:14 UTC
Not sure what firmware version and I haven't seen this myself ever. But here's the report from CAT:

Scenario 1:

Plug into power. Unit boots (logitech logo, "free your music" screen - no sound,  then screen goes black.)  No sound at any time, no touchscreen response.  Hit reset button, same sequence repeats. Remove power, wait 30 seconds same response.

So, naturally, On to factory reset (Scenario 2):

Hold reset button in for a few seconds to factory reset.    Screen shows logitech logo, factory settings restored screen, then the free your music screen (with sound this time!), on to language setting, looks normal, connect to wireless, enter WEP2 key, "connecting to" screen, progresses to "connected to" screen, all normal so far, Squeezebox Account screen indicated currently registered with USER E-MAIL DELETED, OK, select continue, hear a double beep, see home screen BRIEFLY scroll by, then disappears. Black screen, no touch response, no sound.

Hit reset (or remove power), Scenario 1 repeats. Factory reset, Scenario 2 repeats.

press power button multiple times on remote brings it back, and after that resets work just fine.

CAT PR2-0110
Comment 1 Mickey Gee 2010-02-07 23:03:05 UTC
Maybe QA to repro or get unit back? Possibly unit specific.
Comment 2 Michael Herger 2010-02-08 08:02:55 UTC
Run into this issue today (first time). Most interesting log lines:

Jan  1 01:04:07 squeezeplay: INFO   applet.SetupWelcome - SetupWelcomeApplet.lua:468 step9
Jan  1 01:04:07 squeezeplay: INFO   applet.SetupWelcome - SetupWelcomeApplet.lua:140 _setupComplete gohome=false
Jan  1 01:04:07 squeezeplay: INFO   applet.SetupWelcome - SetupWelcomeApplet.lua:113 _enableNormalEscapeMechanisms
Jan  1 01:04:07 squeezeplay: INFO   applet.SetupWelcome - SetupWelcomeApplet.lua:541 network setup complete
Jan  1 01:04:07 squeezeplay: INFO   squeezeplay.applets - AppletManager.lua:709 store settings: SetupWelcome
Jan  1 01:04:07 squeezeplay: INFO   net.slimproto - SlimProto.lua:598 connect to fab4.squeezenetwork.com (74.201.85.104)
Jan  1 01:04:07 squeezeplay: INFO   applet.SlimDiscovery - SlimDiscoveryApplet.lua:508 notify_playerPower: false
Jan  1 01:04:07 squeezeplay: INFO   squeezeplay - JiveMain.lua:200 Turn soft power off
Jan  1 01:04:07 squeezeplay: WARN   applet.ScreenSavers - ScreenSaversApplet.lua:249 The configured screensaver method Clock:openDetailedClockBlack is not available. Falling back to default from Meta file
Jan  1 01:04:07 squeezeplay: INFO   applet.ScreenSavers - ScreenSaversApplet.lua:259 activating BlankScreen screensaver

The device seems to be powering itself off as soon as it can connect to mysb.com. Might be related to some alarm fallback code?

Also: we should use a reasonable default value. The current setting seems to be broken, and falling back to Blank seems like a rather confusing/scary choice...
Comment 3 Michael Herger 2010-02-08 08:03:36 UTC
Created attachment 6500 [details]
full log from during factory reset
Comment 4 Michael Herger 2010-02-08 08:04:13 UTC
if this indeed is due to some alarm fallback we might make sure it's not broken in 7.4.2 too...
Comment 5 Ryan 2010-02-08 08:49:28 UTC
I have one here that did the same thing. I even rewrote the file system with the same results described for senario1 and 2. 

used the remote as described and it's back.   

I had been testing tiny SC with SD card and USB just before it the symptoms appeared. Not sure exactly which actions though.
Comment 6 Michael Herger 2010-02-08 09:18:42 UTC
Steps to reproduce:

- connect to fab4
- (soft) power off the device
- press & hold reset button to initiate a factory reset
- go through setup until device has network connectivity
-> it will connect to mysb.com and restore the previous power state which was off
Comment 7 Ryan 2010-02-08 10:20:29 UTC
I used your steps to reproduce. did it multiple times.
1st time the unit reset and had to proceed through the setup process then got the black screen and recovered with remote

2nd time held for less time 3 sec got the black screen mode recovered with remote, when it came back I did not have to redo setup.

3rd time same a second but recovered by the touch screen. pressing the upper left .
Comment 8 Ben Klaas 2010-02-08 12:03:48 UTC
These five lines fully encapsulate the problem:

Jan 25 21:36:49 squeezeplay: INFO   squeezebox.server - SlimServer.lua:691 connected mysqueezebox.com

Jan 25 21:36:49 squeezeplay: INFO   applet.SlimDiscovery - SlimDiscoveryApplet.lua:508 notify_playerPower: false

Jan 25 15:36:49 squeezeplay: INFO   squeezeplay - JiveMain.lua:200 Turn soft power off

Jan 25 15:36:49 squeezeplay: WARN   applet.ScreenSavers - ScreenSaversApplet.lua:249 The configured screensaver method Clock:openDetailedClockBlack is not available. Falling back to default from Meta file

Jan 25 15:36:49 squeezeplay: INFO   applet.ScreenSavers - ScreenSaversApplet.lua:259 activating BlankScreen screensaver


1. connect to mysb.com during setup
2. playerPower notification comes through that power is off (as according to mysb.com)
3. squeezeplay turns soft power off
4. black clock screensaver doesn't kick in because clock hasn't been set yet (by design)
5. falls back to default when off screensaver, blank screen

note that I could not reproduce this bug when a local server is running.

I think that 4 and 5 are actually working as they should, but we've been led to those steps erroneously. Soft off should never happen during setup. So, I'll target points 2 and 3 there and see where the best place to fix is.
Comment 9 Ben Klaas 2010-02-08 12:52:14 UTC
I added an isSetupDone method that can be called from SlimDiscovery, but unfortunately it's now a race condition and the wrong winner wins...

Jan 25 16:14:23 squeezeplay: INFO   applet.SetupWelcome - SetupWelcomeApplet.lua:552 network setup complete
Jan 25 16:14:23 squeezeplay: INFO   squeezeplay.applets - AppletManager.lua:709 store settings: SetupWelcome

--- setup now stored as complete

Jan 25 16:14:23 squeezeplay: INFO   net.slimproto - SlimProto.lua:598 connect to fab4.squeezenetwork.com (74.201.85.104)
Jan 25 16:14:24 squeezeplay: INFO   applet.SlimDiscovery - SlimDiscoveryApplet.lua:508 notify_playerPower: false

--- then the playerPower notification comes and sets the power to off. since setup is recorded as done, the screensaver again kicks in immediately.

Jan 25 16:14:24 squeezeplay: WARN   applet.SetupWelcome - SetupWelcomeApplet.lua:69 Setup is complete! true
Jan 25 16:14:24 squeezeplay: INFO   squeezeplay - JiveMain.lua:200 Turn soft power off
Jan 25 16:14:24 squeezeplay: WARN   applet.ScreenSavers - ScreenSaversApplet.lua:249 The configured screensaver method Clock:openDetailedClockBlack is not available. Falling back to default from Meta file
Comment 10 SVN Bot 2010-02-08 13:30:09 UTC
 == Auto-comment from SVN commit #8464 to the  repo by bklaas ==
 == https://svn.slimdevices.com/?view=revision&revision=8464 ==

Fixed Bug: 15654
Description: fallback screensaver for whenOff is now NONE
Fab4 and Radio both set Black Clock as the default, which is fine. A fallback to that of completely blank, however, is not.
Comment 11 Chris Owens 2010-04-08 17:26:02 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!