Issue metadata
Sign in to add a comment
|
Chrome Remote Desktop shared computer not recieving input
Reported by
henryxpa...@gmail.com,
Nov 30 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS armv7l 8743.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.101 Safari/537.36 Steps to reproduce the problem: 1. Have Windows 10 Insider Preview 2. Open CRD on both devices and register one for remote connections 3. Connect to computer What is the expected behavior? Shared computer should mimic mouse and recieve keyboard input What went wrong? Shared computer does not receive input WebStore page: https://chrome.google.com/webstore/detail/chrome-remote-desktop Did this work before? Yes Unsure - before 10/20/2016 Chrome version: 54.0.2840.101 Channel: canary OS Version: 8743.85.0 Flash Version: Shockwave Flash 23.0 r0
,
Dec 1 2016
Could anyone from chromoting team please have a look into this issue. Thanks...!!
,
Dec 2 2016
As per the Comment# 0, looks issue reported in Chrome OS.
,
Dec 6 2016
Can we get confirmation of the webstore link? The one mentioned doesn't work. I'm not familiar with Windows 10 Insider Preview. Is it some sort of early access version of Windows?
,
Dec 12 2016
1. Updated Link: https://chrome.google.com/webstore/detail/chrome-remote-desktop/gbchcmhmhahfdphkhkmpfmihenigjmpp?utm_source=gmail 2. This is not just a chrome OS problem, I haven't been able to control my desktop on either my chromebook or my android phone. 3. Windows 10 Insider preview is indeed an early access version of windows, with the newest features available sooner. Like Canary. 4. TeamViewer works just fine, this is indeed a Chrome Remote Desktop problem
,
Dec 12 2016
Joe, can we get a Windows 10 Insider Preview install to test with? Do we need more information before trying to repro?
,
Dec 12 2016
I know AJ did at one time. AJ, do you still have a machine with the insider builds that we can try this on? If so, can you capture a log for the repro?
,
Dec 12 2016
I don't currently have it set up, but can do so. henryxparker: which release ring are you on, and what build is currently installed? And do you happen to know around what date the issue started occurring?
,
Dec 12 2016
I'm on the fastest release schedule. Build: 14965.rs_prerelease.161104-1700 Not completely sure when it started. I'm 90% sure it happened sometime after July of this year and before October.
,
Dec 14 2016
Apologies for the delay - it took some time to trigger, download and install the insider update. Unfortunately, I chose the fast ring and downloaded a build later than what you have currently installed. It is 14986.1000. I am unable to reproduce the issue on this build. Can you make sure you are on the fast ring, and trigger a download of the latest build (by checking for Windows updates)? After this, see if the issue still reproduces
,
Dec 15 2016
,
Dec 16 2016
There was a bug with my Insider prieview build that did not allow updates to appear. I'm going to revert to an older build, so I can update to the newest one, and I will attempt to reproduce the bug.
,
Dec 16 2016
Updated to 14986. Reproduced bug with both my android app and from my chromebook. Do you want some video proof?
,
Dec 16 2016
Let's start with some debug logging from the host machine. Can you capture a log from the host machine using the instructions at https://productforums.google.com/d/msg/chrome/RMpoN0WEpzg/0yvbde0ZIFkJ, specifically the section titled 'Recording an ETW trace'. Steps: 1.) Open an admin cmd prompt and type 'net stop chromoting' 2.) Begin the ETW capture steps from the link above 3.) In the admin window, type 'net start chromoting' 4.) Run your scenario and reproduce the issue 5.) Stop the ETW capture and attach the output to this bug With respect to the scenario, it sounds like you can connect to the host and view the remote desktop. Is all input injection broken (i.e. mouse doesn't move (i.e. hover state is never activated) mouse clicking fails, keyboard input fails)? It would be good to know what you have tried (especially during the repro above) and what is/isn't working.
,
Jan 4 2017
Quick ping since it has been a few weeks. Can you grab a log from the host if the problem is still occurring? Thanks!
,
Jan 20 2017
Resolving since we can't repro in house and don't have the info needed to proceed with the investigation. If you can gather the requested logs, please reactivate and attach them. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Nov 30 2016Labels: M-54