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

Issue 738274 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Glimmer's screen goes dark in guest mode or after signing out of user session

Project Member Reported by jingwee@chromium.org, Jun 30 2017

Issue description

Chrome Version: M61.0.3144.0 dev glimmer
OS: ChromeOS 9693.1.0

What steps will reproduce the problem?
Either enter VT2, sign in as Guest or sign out from a user session.

What is the expected result?
You can see the display.

What happens instead?
The screen goes dark. When shinning a light on the screen and look closely, the display is still there as if it is no longer back lit. The brightness button does not help.  Need to reboot the device to resume the  display.

This issue is only reproducible on Glimmer and does not happen on other devices such as elm and reks.  Two Glimmers were tested.

This issue begins from M61.0.3138.0:9690.0.0 dev glimmer.

This issue does not reproduce in M60.0.3112.50:9592.37.0 beta glimmer.

 
Cc: abod...@chromium.org ka...@chromium.org
Components: UI
Labels: -Type-Bug -Pri-3 ReleaseBlock-Beta M-61 Pri-2 Type-Bug-Regression
Feedback report from guest mode: 67220060138
Owner: hennessywill@chromium.org
Sounds like a display issue - Will are you the right assignee?
Status: Assigned (was: Available)
Components: -UI OS>Kernel>Display
Cc: pucchakayala@chromium.org
Labels: -Pri-2 Pri-1
Reproduce the issue on Chrome 61.0.3163.16/CrOS 9765.12.0 - Glimmer.  After signing out from user accounts, the screen goes black. Brightness key doesn't work.  
This works fine on ToT on glimmer (62.0.3166.0), is this only broken on 61?
It is only broken in M61.  Tested and still reproduced in M61.0.3163.16:9765.12.0 dev glimmer.

Not reproduced in M60 and M62 (62.0.3169.0:9795.0.0).

Confirmed the issue began from M61.0.3138.0:9690.0.0 dev.

The issue was not reproduced in the previous build M61.0.3138.0:9688.0.0 dev.

Components: -OS>Kernel>Display
Status: WontFix (was: Assigned)
no problem on glimmer on 61.3163.20.
Cc: marc...@chromium.org
Status: Assigned (was: WontFix)
Still reproduced in
9765.16.0	61.0.3163.30
9765.15.0	61.0.3163.20
9765.13.0	61.0.3163.20

Reproduced on two Glimmers DVT.  One managed and one unmanaged.

Video: https://drive.google.com/a/google.com/file/d/0B6gObwYapS4UMGN4ZzJoaTJCajA/view?usp=sharing
Resharing the video with permission fixed:
https://drive.google.com/file/d/0B66sLSSfR23oUXViZmVIWE1LdG8/view?usp=sharing

We need a new owner since Will moved on.   

Can we push this one a bit?  Trying to close Beta blockers for M61.  Thanks bunches,
Ping since we're planning a Beta release next week.  Can we escalate since this is tagged as a beta blocker?  Thanks.

Owner: marc...@chromium.org
Stéphane Marchesin called out that this is being fixed by Intel (per my IM); need to monitor / test / unblock.  Reassigning since Will is no longer on CrOS.
Hi all, we're targeting a Beta next week so we need fixes and/or workarounds submitted by COB Monday 8/14 if this is still considered a beta blocker.  Possible?  Have who / what we need to move this forward?   Thanks!
Mergedinto: 737945
Status: Duplicate (was: Assigned)

Sign in to add a comment