New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 783209 link

Starred by 2 users
Status: Duplicate
Owner:
█ benzh@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
atwilson@chromium.org
xiy...@chromium.org
snanda@chromium.org
█ sduraisamy@chromium.org
█ dskaram@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Devices reporting crashes and failing to load kiosk app after updating to R62

Reported by google.a...@wandcorp.com, Nov 9 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.30 Safari/537.36
Platform: 9901.66.0 (Official Build) stable-channel ninja

Steps to reproduce the problem:
1.Allow update to R62 to occur
2.Restart device from kiosk app
3.Device crashes and falls into suspend mode

What is the expected behavior?
device updates and loads kiosk app

What went wrong?
A high percentage of the initial devices to take the R62 release reported crashes and failed to load kiosk app on restart.

Have since pinned all OS to R61 on manged devices

Did this work before? Yes R61

Chrome version: 63.0.3239.30  Channel: stable
OS Version: 62.0.3202.82
Flash Version: 

Did not impact all devices, but did impact majority. Believe the devices restarted and hung on white app initializing screen, and feel into suspend mode. Difficult to confirm remotely. Logs attached from two devices.
logs_20171109-0603 (1).zip
267 KB Download
logs_20171109-0643 (1).zip
309 KB Download

Comment 1 by google.a...@wandcorp.com, Nov 10 2017 

From what I am being told by the manufacturers;

There is a definite issue with the screen controllers with ASUS and Aopen devices. If a device is allowed to update to R62 the chromebox will likely start displaying a black screen.

This issue should be upgraded and addressed.

Comment 2 by sduraisamy@chromium.org, Nov 15 2017

Cc: xiy...@chromium.org sduraisamy@chromium.org atwilson@chromium.org snanda@chromium.org dskaram@chromium.org
Components: Enterprise
Labels: -Pri-2 M-63 ReleaseBlock-Stable Pri-1
Owner: benzh@chromium.org
Status: Assigned (was: Unconfirmed)
Ben, it looks like this issue is related to the HDMI issue.

Comment 3 by benzh@chromium.org, Nov 15 2017

Mergedinto: 780122
Status: Duplicate (was: Assigned)
Yes it's the same issue.
►

Sign in to add a comment