Issue metadata
Sign in to add a comment
|
Chrome Sign Builder displays only white screen under ChromeOS 60
Reported by
jsm...@stillwaterschools.com,
Aug 7 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Platform: 9592.71.0 (Official Build) stable-channel veyron_mickey firmware 6588.264.0 Steps to reproduce the problem: 1. set up OU with Chrome Sign Builder with policy for google presentation 2. move brand new chromebit into OU with other working chromebits 3. boot up Chromebit, see expected CSB loading screen with 'please wait' 4. Screen goes blank white (not the "no policy detected" screen either). Mouse pointer is visible and active. What is the expected behavior? Slideshow should be displayed What went wrong? Beats the heck out of me. I've tried moving the Chromebit to a different OU that is using RiseVision, and that pulled up just fine. Only the Chrome Sign Builder isn't running. Every other Chromebit in the same OU is running 59. Could this be a weird regression in 60? Did this work before? Yes 59 Chrome version: 60.0.3112.80 Channel: stable OS Version: 60.0.3112.80 Flash Version:
,
Aug 8 2017
,
Aug 9 2017
I tried reproducing the problem on a device with ChromeOS 60 and so far don't observe the issues you have. Would you mind sending us the application configuration (schedule) you are trying to use (if you prefer you can also email it to me instead of uploading it here). Have you tried configuring a different schedule instead of the one that fails?
,
Aug 9 2017
Also please share whether the option to let the app to manage the power settings of the device is turned on or off in the admin panel for this OU.
,
Aug 9 2017
Schedule is attached. I did try removing the schedule and reapplying it, no change. The app is allowed to manage power. (Kiosk app, installed automatically, automatic launch, etc)
,
Aug 10 2017
Thanks for sharing the schedule. I noticed that you have the URL for the presentation entered twice - once as a background url and once as a scheduled item (6am to 7pm ET?). The scheduled item url is correct while the background url seems to be malformed (results in a document not found error). Otherwise the schedule works on my test device. I am trying to get hold of a Chromebit to test with it if it is a local issue to this particular device. Meanwhile please try the schedule attached to this post and let us know if it works for you. You should see http://example.com loaded when it is active.
,
Aug 17 2017
That seems to have fixed the schedule, yes. Thank you for noticing that! I'm not very keen to update a Chromebit back to R60 to see if it will break or not, as I have no spares and these are all production units at the moment.
,
Aug 28 2017
Marking this as WontFix for now since the problem is not reproducible. Please comment here if further investigation is needed. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jsm...@stillwaterschools.com
, Aug 7 2017