New issue
Advanced search Search tips

Issue 855877 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
chrome-os-gcon-escalation@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Remote Desktop fails to connect

Reported by the.mada...@gmail.com, Jun 23 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.125 Safari/537.36
Platform: 10718.29.0 (Official Build) beta-channel veyron_minnie

Steps to reproduce the problem:
1. Open Chrome Remote Desktop app.
2. Click pre-existing connection, listed online, to connect.
3. Cannot connect on Chrome OS/Chromebook. Can connect at same moment to said remote desktop via iPhone Remote Desktop app. 

What is the expected behavior?
Connect to the remote desktop.

What went wrong?
Could not connect. "unexpected error, please report to developers." Cannot set it up as a new connection either.

Did this work before? Yes Problem new since latest beta update, last connected successfully 6/21 AM prior to update.

Chrome version: 65.0.3325.125  Channel: beta
OS Version: 68.0.3440.34
Flash Version:

Comment 1 by trumbull@chromium.org, Jun 26 2018

Components: Services>Chromoting
Labels: Hotlist-ConOps-CrOS
Related user feedback reports, with logs:
- http://listnr/product/208/report/85515227322
- http://listnr/product/208/report/85515221421

Modem Status:
[0623/122802:ERROR:object_proxy.cc(582)] Failed to call method: org.freedesktop.ModemManager.EnumerateDevices: object_path= /org/chromium/ModemManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.ModemManager was not provided by any .service files
[  ]

Comment 2 by jamiewa...@chromium.org, Jun 26 2018

Status: WontFix (was: Unconfirmed)
I have responded to the user with the following. We'll track any replies via website feedback.

Unfortunately, the ChromeOS feedback mechanism doesn't include enough logs for us to track down the problem. Your best option is to try the new Chrome Remote Desktop website, https://remotedesktop.google.com/access. If that doesn't work, please submit feedback using the link at the bottom of that page, which will include a lot more debugging information.

If you don't mind, it would also be useful to get specific logs from the Chrome Remote Desktop app, although this is a bit more involved. The steps are below:

* Launch the app, reproduce the problem, then visit chrome://extensions in another tab.
* 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.
* Copy/paste the contents of that tab into a reply to this email.

Finally, if you just want a quick fix for the problem, we've had some reports of this error message in the past where rebooting the router/modem has helped.
►

Sign in to add a comment