New issue
Advanced search Search tips

Issue 842881 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Keyboard is not working on TOT

Project Member Reported by abod...@chromium.org, May 14 2018

Issue description

Chrome OS 10678.0.0, 68.0.3429.0 Kevin and BOB

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)Install recovery stick
(2)Complete OOBE and try to enter user id/password at login screen.

Expected Result:

Actual Result:
Unable to enter user id /password with Keyboard. 
But on-screen keyboard works fine.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Summary: Keyboard is not working on TOT (was: Unable to enter user id /password at login screen)
After login with on-screen keyboard still built-in keyboard is not working.
Components: -UI>Shell>StartScreen IO>Keyboard
Cc: jkardatzke@chromium.org
The only key combination that does anything after you are in Chrome OS that I've found in this scenario is Refresh + Power. That will reboot it (as well as with Esc to go to recovery mode).  But I'm guessing those are intercepted by something lower level.
Cc: adlr@chromium.org
IIRC refresh+pwr and esc+refresh+pwr are handled by the EC.
Cc: zentaro@chromium.org
Owner: jdufault@chromium.org
Any chance this is related to the other login UI misbehavior?

We are hoping to promote to beta next week so we need this to get fixed soon.
We are trying to go to beta this week, we need this fixed in the next 24 hours.
Cc: jdufault@chromium.org
Owner: adlr@chromium.org
I'd be very surprised if this was related to login, sounds like a platform issue.

adlr@ do you know who can take a look at this?

Comment 9 by kinaba@chromium.org, Jun 12 2018

I guess this is a dup of https://bugs.chromium.org/p/chromium/issues/detail?id=843013
that fixed already few days after the regression

Status: WontFix (was: Untriaged)
Thanks for finding that, sounds like a WontFix to me.

Sign in to add a comment