New issue
Advanced search Search tips

Issue 891679 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Pixel 2013 - BLACK screen for 10 seconds following password input

Reported by scottt...@gmail.com, Oct 3

Issue description

Chrome Version       : 63.0.3239.140
OS Version: 10032.86.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. Boot the Pixel 2013
2. Input password
3. Screen immediately goes blank for 10+ seconds

What is the expected result?
It should boot normally like it always has until this final EOL update

What happens instead of that?
The screen blanks for 10+ seconds following password input

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 10032.86.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.140 Safari/537.36

Yes, I realize that that the 2013 just hit EOL - which frankly is pathetic considering it was Google's own $1000+ flagship.

This new blank screen feature suddenly arriving just at the end of life seems quite honestly just too coincidental.  The 2013 has NEVER done this before.  It operates completely normally with the exception of the new "feature" that causes the user to wait and wonder if it's even going to boot or if something went wrong.

I do not think it's asking too much to suggest that Google should FIX this regardless of the EOL status.

 
 
No kidding, this only showed up with the latest EOL update.  I got the EOL notifications and finally disabled them.  Aside from that it is running normally but the blank screen period lasts longer than the entire normal boot sequence!
Tested again today.  Actually closer to a 15s blank screen following password input!

Please tell me that the most expensive Chromebook ever made isn't going to be left in this state.


This is completely repeatable on the 2013 Pixel.  Following password input, the screen blanks for close to 15s EVERY TIME!  

I have 3 Chromebooks on this account.  Samsung CB2, HP Chromebook 14 and the Pixel.  Only the Pixel exhibits this new blank screen following login.  I have never seen this on any Chromebook and have used quite a number of them.
I stand corrected.  I had not done any updates on my Samsung CB2 or HP 14" in a while.  After updating both of those machines, they are ALL doing the black screen after login for differing periods of time.  This time period seems to correspond to how fast the Chromebook generally is in processing.  The Samsung takes almost 20+ seconds to return from the black screen, the Pixel 2013 around 15, and the HP 14" about 12.

This is clearly a bug introduced in the latest ChromeOS that affects multiple if not all Chromebooks.

All three are now running the same OS version.

Pixel 2013 - 69.0.3497.95
Samsung CB2 - 69.0.3497.95  
HP 14" - 69.0.3497.95

While I assume this bug will be fixed in a coming revision for the Samsung and HP I worry that since Google has abandoned the Pixel 2013 it will be left with this bug that virtually TRIPLES the boot time.  

I would think any objective party would see that this is not at all an acceptable state to leave the Pixel 2013 in.  Regardless of it's new EOL status, The Pixel 2013 should be updated with the next rev that fixes this glaring OS bug that extends boot times degrading the user experience significantly.


Another thing to note.  I have not changed the extensions in months.  The only thing that changed lately was the OS update.
Components: UI>SignIn
Verified this again with a different account on the same Pixel 2013.  The post-login black screen remains for the same duration for a different account.
This is almost certainly the same as Issue 831549

https://bugs.chromium.org/p/chromium/issues/detail?id=831549&q=acer%2015&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

Please restore my faith in Google and tell me that Google isn't simply going to leave their $1000+ Chromebook in this broken state.


At least some of you are out only $1000... which still isn't right.  We have well over $100,000 worth of Chromebooks with this delayed startup issue.

As already reported in Issue 831549.

We have the following devices:
Dell 13-7310
HP 11 G5 
Acer C720-2103
Acer C740-C4PE

Only the Acer C740 devices have the issue of delayed startup.  These devices take almost exactly 15 seconds from the time you open the lid to the Chrome logo startup screen.

All Devices are on OS Version 70.0.3538.110
Bug report was already submitted, I put "bug issue 831549" in the description as well as a link to https://bugs.chromium.org/p/chromium/issues/detail?id=831549.

Sign in to add a comment