New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 605011 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 539742



Sign in to add a comment

Running udevadm trigger --subsystem-match=input --action=change loses input devices

Project Member Reported by drinkcat@chromium.org, Apr 20 2016

Issue description

Version: Probably everything since R45...
Board: cyan, but most (all?) boards seem to be affected

What steps will reproduce the problem?
(1) udevadm trigger --subsystem-match=input --action=change

What is the expected output?

Input (mouse/keyboard) still works.

What do you see instead?

No more input (mouse/keyboard).

This appears in /var/log/messages, but that may not be the issue:
2016-04-20T15:00:24.250202+08:00 NOTICE logger[29766]: /opt/google/input/device_added 
2016-04-20T15:00:24.259052+08:00 NOTICE logger[29777]: /opt/google/input/device_added /dev/input/event6
 
Somewhat related to Issue 539742, but this seems to be the true cause

Arguably, one possible solution is also "Do not do that ,-)". We are implementing a workaround in https://github.com/dnschneid/crouton/pull/2541 .

Comment 2 by vapier@chromium.org, Apr 22 2016

Blocking: 539742
i suspect it's entirely an issue in Chromium
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 24 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: IO>Keyboard

Sign in to add a comment