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

Issue 784897 link

Starred by 1 user
Status: Duplicate
Merged: issue 776613
Owner:
wutao@chromium.org
Closed: Nov 2017
Cc:
r...@chromium.org
█ reve...@chromium.org
wzang@chromium.org
jdufault@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

login screen solid blue with "fire" images in random boxes

Reported by jsm...@stillwaterschools.com, Nov 14 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Platform: 9765.85.0 (Official Build) stable-channel reks

Steps to reproduce the problem:
1. open Chromebook
2. see bizarreness
3. reboot to clear and resume normal operation

What is the expected behavior?
no crazy screen

What went wrong?
Entirely unclear. These are Lenovo N42-20 Chromebooks, running with a public session, but this happens before a login to anything is ever attempted. Purely randomly, hard to reproduce. Screenshot attached.

I'll grab logs of an affected machine if someone will tell me exactly what/where to grab. Lenovo's answer so far has been "powerwash". (These are managed Chromebooks, so we use recovery tool to refresh them new.)

Did this work before? Yes Didn't see this before r60 at least.

Chrome version: 61.0.3163.123  Channel: stable
OS Version: 	Google_Reks.7287.133.81
Flash Version:
20171101_111211.jpg
3.3 MB View Download
20171101_111302.jpg
2.9 MB View Download

Comment 1 by r...@chromium.org, Nov 14 2017

Cc: r...@chromium.org jdufault@chromium.org reve...@chromium.org wzang@chromium.org
Components: -UI UI>Shell>StartScreen
Owner: wutao@chromium.org
Status: Assigned (was: Unconfirmed)
Could this be related to blur?

Comment 2 by wutao@chromium.org, Nov 14 2017

Mergedinto: 776613
Status: Duplicate (was: Assigned)
Reks is "strago" family with kernel 3.18.
Powerwash will not resolve the problem. This happens occasionally only at non-dev mode.
It is due to GPU hang so tile uses wrong texture. But what cause the GPU hang is unknown.

In another  issue 776613 , some investigations think it is due to the kernel change for kernal 3.18.

Comment 3 by jsm...@stillwaterschools.com, Nov 14 2017 

Sounds like a match with 776613.

Comment 4 by wutao@chromium.org, Nov 14 2017 

jsmith@, I also think so.

If you like to provide some logs, you can still type password to enter system when this happens. And then you can file a report by "alt+shift+i" with system information so that we can double check.

You also can type file:///var/log/messages in browser location bar to see the log. You should find "GPU hang" error in the log when this happens.
►

Sign in to add a comment