New issue
Advanced search Search tips

Issue 657006 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

[Chrome OS] Touchpad not working

Project Member Reported by hernandezma@chromium.org, Oct 18 2016

Issue description

Chrome OS version:
8530.81.0 Stable
8743.65.0 Beta

Devices make/model 
HP Chromebook 11 G4 EE 

Hardware ID: 
KIP C8A-G4G-P4A-A6A-A2T 

Domain managed devices? 
Yes 
|======Issue Definition======| 
Touchpad not working.

What steps will reproduce the problem?
(1) Take a new Chromebook from the model above.
(2) Update to current stable.
(3) Restart and try to use it normally, issue comes up.

Issue background:
The Chromebooks were purchased back in May and never used, when devices started to be used in September. It’s not clear if the touch-pad started to fail due to the update to current stable, and the Admin contacted the manufacturer, which advised to update to current Dev version, which fixes the problem.

What's the expected behavior? 
Touchpad should work.

What's the actual result? 
Touchpad is not working. 

Timeframe when issue started: 
When devices were being prepared for use in September 2016. 

Does it affect all devices? 
300 out of 3000 were tested so far and they all had the same problem 

Isolated to: 
HP Chromebook 11 G4 EE only.


|======Troubleshooting and Workaround======| 
- Troubleshooting steps taken: 
1- Wiped device. 
2- Used recovery USB.
3- External mouse works.

Is this reproducible in Beta/Dev?  
It reproduces in Beta, but not in Dev (8743.65.0 Dev).

Existing Workaround: 
Move to Dev channel 

|======Devices logs (Google restricted) ======|
Logs from the 3 release channels can be found here:
https://drive.google.com/open?id=0Bxg-rTzA58PeOUNETkZuLXduME0

Related info:
This issue was reported before in  crbug.com/616394 , and was fixed, but seems that either it’s caused by something else, or the issue reappeared, which I really doubt becasue we would receive more reports, but so far, this is the first one.
 

Comment 1 by yyefet@chromium.org, Oct 18 2016

This issue is being tracked on partner bug:  57508 
Components: Internals>Input>Touch>Pad
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Untriaged)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment