New issue
Advanced search Search tips

Issue 770842 link

Starred by 2 users
Status: Duplicate
Merged: issue 758820
Owner: ----
Closed: Oct 2017
Cc:
derat@chromium.org
xiy...@chromium.org
abodenha@chromium.org
osh...@chromium.org
steve...@chromium.org
jdufault@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Permanent black screen after sign-in screen

Project Member Reported by michae...@chromium.org, Oct 2 2017 
After booting up my samus and attempting to sign in to my corp account, the screen goes black upon submitting my password. It stays black until eventually the computer suspends or powers down.

Attaching a secondary display also shows a black screen on the secondary display. On both displays, the screen is *on*, just black. (ie, the secondary monitor doesn't go to "no input detected" mode.)

This started happening after I rebooted to apply an updated, signed in to my corp account, and was prompted with a different dialog to update the device, hit the button to update, and let the update run for a while. After that reboot this problem began.

I can sign in with my other account on the device, but it gives me the same prompt to update so I don't want to apply that in case it bricks that account too.

Comment 1 by steve...@chromium.org, Oct 2 2017

Cc: derat@chromium.org xiy...@chromium.org osh...@chromium.org abodenha@chromium.org jdufault@chromium.org
I am seeing this since the most recent update to 61.0.3163.110 (beta channel), also only with my @google account. It's a non dev machine so I can not file a feedback report or look at logs.

The next thing I would normally try is removing my @google.com account, but I'm still scratching my head trying to think of what other information I might be able to get off the device. Any suggestions?

Comment 2 by steve...@chromium.org, Oct 2 2017 

And now it no longer repros. My version is still 61.0.3163.110 so no update applied.

Looking at chrome logs in file:///home/chronos/user/log/, I see the following error in recent logs, but not the most recent log:

:ERROR:connection_factory_impl.cc(386)] Failed to connect to MCS endpoint with error -131

Comment 3 by xiy...@chromium.org, Oct 2 2017 

Do we know whether chrome is crashing on the black screen? 

Michael, is it possible to get chrome logs (chrome sys and user, ui log and kernel log)? And are you one the same version as Steven?

Comment 4 by osh...@chromium.org, Oct 2 2017

Mergedinto: 758820
Status: Duplicate (was: Untriaged)
This should be same as  crbug.com/758820 .

Comment 5 by steve...@chromium.org, Oct 2 2017

Mergedinto: -758820 767680
Updatding merged into to the issue that  issue 758820  was merged into :)

Comment 6 by steve...@chromium.org, Oct 2 2017

Mergedinto: -767680 758820
Although, looking at  issue 767680 , I'm not entirely convinced that is the same as  issue 758820  which has different sumptoms, so changing merged-into back.

Comment 7 by steve...@chromium.org, Oct 2 2017 

Failed again, then succeeded. Failure had the "MCS endpoint" error again, success did not.

I don't see any recent non refactoring changes to that file. It could perhaps be a symptom of some other failure though?

Comment 8 by osh...@chromium.org, Oct 2 2017 

758820 is dup of 767680. just fyi.
►

Sign in to add a comment