Issue metadata
Sign in to add a comment
|
Chrome Remote Desktop Does Not Connect
Reported by
lnorto...@gmail.com,
Aug 18 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome Apps 2. Select Chrome Remote Desktop 3. Attempt to Connect to online Host 4. Endless "connecting.." when both are on the same stable connection. What is the expected behavior? To successfully connect. What went wrong? It didn't connect. WebStore page: Chrome Remote Desktop Did this work before? Yes 60 Chrome version: 60.0.3112.101 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 26.0 r0
,
Aug 21 2017
Tested the issue on windows 10 and ubuntu 14.04 using chrome M60 #60.0.3112.101 and M62 #62.0.3192.0 and issue is not reproduced. Remote desktop sharing connection is established successfully and sharing is done. Attached screenshot for reference. @lnorton89-- Could you please try in fresh chrome profile without any extensions and flags enabled and provide us with your observations along with the screencast for better understanding. Thanks!
,
Aug 23 2017
,
Aug 24 2017
Can you attach client logs to this bug? To find the logs: With the app running, visit chrome://extensions Ensure that the "Developer Mode" checkbox at the top right of the page is checked. Scroll down to the Chrome Remote Desktop extension. Click the main.html link.Select the Console tab.
,
Aug 31 2017
Sorry for the delay, haven't been able to get to this. I've just copy/pasted from the console; if there's a better way, please let me know. Tried --enable-logging --v=1 in console with no dice.
,
Aug 31 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 31 2017
Was finally able to connect, here another log showing that.
,
Aug 31 2017
There's nothing obvious in the logs, and we're in the process of replacing this app with something new. I think the best option is to wait for that and see if it resolves the problem.
,
Aug 31 2017
I will say that this only happens on one network but nothing obvious in the network setup / config is appearing to have any cause. I look forward to the new app, I think this is a good compromise. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Aug 18 2017