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

Issue 888068 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome Report Desktop Keyboard Not Working Since Mac OS X Mojave

Reported by jaredbfo...@gmail.com, Sep 21

Issue description

Chrome Version       : Version 63.0.3239.132 (Official Build) (32-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: NA
    Firefox: NA
       Edge: NA

What steps will reproduce the problem?
(1) Access Chrome Remote Desktop
(2) Select a Mac OS X Mojave Remote Desktop
(3) Try to use keyboard. (Mouse works, keyboard does not)

What is the expected result?
Before Mojave (two days ago), the keyboard and mouse worked fine. User was able to unlock the Mac remotely and use the computer as normal.

What happens instead?
The keyboard strokes do not work within the remote desktop. Mouse works as normal, keyboard has no response.

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

 
Labels: Needs-Milestone
Components: Services>Chromoting
Can you give us more information? Are you trying to type at the login screen, or after logging in (and does it make any difference if you are logged in).

Was this an upgrade to Mojave from an earlier install, or a new machine with Mojave on it?

Can you send us host logs? To do that, reproduce the problem, then do the following:

* Open a terminal: Press [Command] + [Space], type Terminal, and press Enter
* Run the following command:

  sudo log show --predicate 'processImagePath contains "ChromeRemoteDesktop"' --info --debug --last 1d > chromoting.log

Cc: krajshree@chromium.org
Labels: Needs-Feedback Triaged-ET
As per comment #3, adding Needs-Feedback label and also requesting reporter@ to please upgrade chrome to latest stable #70.0.3538.67 and please let us know if the issue still persists or not.

Thanks...!!
Status: WontFix (was: Unconfirmed)

Sign in to add a comment