New issue
Advanced search Search tips

Issue 809750 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 819714
Owner: ----
Closed: Apr 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Acer Chromebook 15 CB5-571 gets stuck at sign on Stable, Beta, and Dev Channels

Reported by karenrat...@gmail.com, Feb 6 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10176.65.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.134 Safari/537.36
Platform: 10176.65.0 (Official Build) beta-channel auron_yuna

Steps to reproduce the problem:
1.Turn on computer with lid or power button
2.Try to type in password but cursor sticks for about 30 sec.
3. Everything on screen sticks, but will work after that time of waiting.

What is the expected behavior?
Here is the url for the behavior I have expressed at chromebook-central.
 https://goo.gl/FVNRg4

What went wrong?
A couple of months ago before the updates, everything was fine on Stable channel when turning on chromebook and signing in. When the new updates came, the sticking of the cursor when trying to type in my password came into existence. I was advised to try the Beta Channel because of the newer updates. It seemed to work for awhile, but the sticking started again. I tried the Dev channel. It does the same there. When I do a Recovery or a Power Wash, the "welcome" screen sticks some seconds there. The sign in will be good for a couple of times, but it will go back to sticking after that. I have been in Developer Mode and back again, and still the same effect. Screen shots don't really show anything. I couldn't take one anyway, everything is frozen at sign-in. The internet can be on successfully too. I have even tried this with the internet turned off at sign-in, still the same.

Did this work before? N/A 

Chrome version: 64.0.3282.134  Channel: beta
OS Version: 10176.65.0
Flash Version: 28.0.0.161 /run/imageloader/PepperFlashPlayer/libpepflashplayer.so
 
Components: OS>Crouton
The first time I put Ubuntu on, I didn't delete crouton when I did a Chromebook Recoveery. The second time I put Ubuntu on, I did delete crouton. I had deleted the chroot by using command: sudo delete-chroot xenial. I've been back on Stable out of Developer Mode now.
I went back in developer mode to check if there was any more crouton or mounts, and it doesn't come up.
Components: -OS>Crouton
crouton doesn't persist past dev wipes, power washes, or recovery.
Mergedinto: 819714
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment