Issue 468121 in chromium: Chrome Remote Desktop Host Preferences Can't be "Enabled"

135 views
Skip to first unread message

chro...@googlecode.com

unread,
Mar 17, 2015, 7:29:02 PM3/17/15
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Cr-Platform-Extensions Pri-2 Via-Wizard Type-Bug OS-Mac

New issue 468121 by brian.ro...@gmail.com: Chrome Remote Desktop Host
Preferences Can't be "Enabled"
https://code.google.com/p/chromium/issues/detail?id=468121

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2336.0 Safari/537.36

Steps to reproduce the problem:
1. After installing and accessing the extension, clicking on the "Enable
remote connections" button
2. It prompts for a new PIN #, twice
3. It launches the System Preferences app, loaded to the Chrome Remote
Desktop Host Preferences applet prompting for the PIN # again
4. After clicking the lock icon to unlock System Preferences and
authenticate as an admin user, allowing changes, enter the PIN # and click
Enable
5. System Preferences app with the Chrome Remote Desktop Host Preferences
applet shows, "Remote connections to this computer are disabled." and the
button "Disable Remote Connections" is greyed out.
6. Back in the Chrome tab with the Chrome Remote Desktop extension running,
a window pops-up saying, "Remote connections for this computer have been
enabled."
7. After clicking "OK," the computer shows up in the list, but as soon as
you refresh the list the newly added computer is immediately greyed out and
has a "(last online xx:xx:xx)" timestamp message

What is the expected behavior?
1. Corresponding to #5 in the Steps to reproduce the problem, it should say
that remote connections are enabled.
2. Corresponding to #7 above, the newly added computer should remain
available.

What went wrong?
Remote connections for the newly added computer are not actually enabled.

WebStore page:
https://chrome.google.com/webstore/detail/chrome-remote-desktop/gbchcmhmhahfdphkhkmpfmihenigjmpp

Did this work before? Yes Hard to say, sorry. I've used Canary as my main
driver for a long time and it "used to work." ;-)

Chrome version: 43.0.2336.0 Channel: canary
OS Version: OS X 10.10.2
Flash Version: Shockwave Flash 17.0 r0

See http://youtu.be/JMBV_JP6ATg for a video of the process that fails.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Mar 24, 2015, 7:31:47 PM3/24/15
to chromi...@chromium.org

Comment #4 on issue 468121 by dcai...@chromium.org: Chrome Remote Desktop
Brian/keltik: could you please try enabling your hosts again, and then
attaching the following file to this bug:

/var/log/org.chromium.chromoting.log

Thanks in advance for your help!

chro...@googlecode.com

unread,
Apr 9, 2015, 9:27:38 PM4/9/15
to chromi...@chromium.org

Comment #7 on issue 468121 by bugdro...@chromium.org: Chrome Remote Desktop
Host Preferences Can't be "Enabled"
https://code.google.com/p/chromium/issues/detail?id=468121#c7

The following revision refers to this bug:

https://chromium.googlesource.com/chromium/src.git/+/25cef11863014bc8ff4a8ff16d8570ad9c62bedc

commit 25cef11863014bc8ff4a8ff16d8570ad9c62bedc
Author: dcaiafa <dca...@chromium.org>
Date: Fri Apr 10 01:07:10 2015

Change logging to use syslog; fix CRD in Yosemite

Have the Chromoting host write logs to syslog. This works around the
issue where, in some Yosemite configurations, launchd fails to start the
agent if the user running the agent does not have write access to the
log or the log's directory.

Logging to syslog has additional advantages such as:
- Log rotation and overflow are now managed by the system.
- Messages are read-restricted to the user running the agent.

After this change, logs will no longer be stored in
/var/log/org.chromium.chromoting.log. To obtain logs, use the following
command:

sudo syslog -k Facility org.chromium.chromoting

If 'sudo' is omitted, messages logged in the login screen (while the
agent is running as root) will not be available.

N.B. The changes to ChromotingHostService.pkgproj were made using
the 'Packages'
program. To test the changes, I built and installed a .dmg from scratch.

BUG=468121

Review URL: https://codereview.chromium.org/1073883002

Cr-Commit-Position: refs/heads/master@{#324550}

[modify]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/host/installer/mac/ChromotingHostService.pkgproj
[delete]
http://crrev.com/3e7d0b1ed55adb4c483edefcf0802b334e732316/remoting/host/installer/mac/Config/org.chromium.chromoting.conf
[modify]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/host/installer/mac/LaunchAgents/org.chromium.chromoting.plist
[modify]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/host/installer/mac/Scripts/remoting_postflight.sh
[rename]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/host/logging_linux.cc
[add]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/host/logging_mac.cc
[modify]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/remoting_host_mac.gypi
[modify]
http://crrev.com/25cef11863014bc8ff4a8ff16d8570ad9c62bedc/remoting/remoting_host_srcs.gypi

chro...@googlecode.com

unread,
Apr 10, 2015, 9:14:30 PM4/10/15
to chromi...@chromium.org
Updates:
Labels: -Merge-Requested Merge-Approved Hotlist-Merge-Approved

Comment #12 on issue 468121 by lafo...@google.com: Chrome Remote Desktop
Host Preferences Can't be "Enabled"
https://code.google.com/p/chromium/issues/detail?id=468121#c12

Approved for M43 (branch: 2357)

chro...@googlecode.com

unread,
Apr 14, 2015, 1:55:33 AM4/14/15
to chromi...@chromium.org
Updates:
Labels: TE-Verified-43.0.2357.18 TE-Verified-M43

Comment #15 on issue 468121 by a...@chromium.org: Chrome Remote Desktop
Verified the merge on the latest M-43(43.0.2357.18
-refs/branch-heads/2357@{#75}) as per the steps in C#0 and as performed in
the demo video on Mac OS 10.9.5.

Newly added computer isn't disabled and doesn't get disabled even after
refresh of the 'My Computers' section.

chro...@googlecode.com

unread,
May 7, 2015, 9:37:22 PM5/7/15
to chromi...@chromium.org

Comment #18 on issue 468121 by ajnol...@chromium.org: Chrome Remote Desktop
brian.ropers.huilman: Does this appear to be fixed for you?

chro...@googlecode.com

unread,
May 12, 2015, 9:16:20 PM5/12/15
to chromi...@chromium.org
Updates:
Cc: dcai...@chromium.org

Comment #21 on issue 468121 by dcai...@chromium.org: Chrome Remote Desktop
Issue 483451 has been merged into this issue.

chro...@googlecode.com

unread,
May 12, 2015, 10:03:17 PM5/12/15
to chromi...@chromium.org

Comment #22 on issue 468121 by brian.ro...@gmail.com: Chrome Remote Desktop
I downloaded the M43 image and it worked great! The fix works. Thanks so
much!

chro...@googlecode.com

unread,
May 12, 2015, 11:32:22 PM5/12/15
to chromi...@chromium.org

Comment #23 on issue 468121 by rs.hol...@gmail.com: Chrome Remote Desktop
M43 works for me as well, thank you!

chro...@googlecode.com

unread,
Jun 15, 2015, 10:10:57 AM6/15/15
to chromi...@chromium.org

Comment #26 on issue 468121 by Doug.Bag...@gmail.com: Chrome Remote Desktop
Confirmed. Works for me as well.

chro...@googlecode.com

unread,
Jun 23, 2015, 9:46:32 AM6/23/15
to chromi...@chromium.org

Comment #27 on issue 468121 by rs.hol...@gmail.com: Chrome Remote Desktop
On another MacBook, this issue is NOT fixed. I have downloaded and
installed 43.0.2357.39. In the Remote Access app two other Macs previously
set up appear, but the local computer does not, and in the Remote Access
prefs pane it says "Remote connections to this computer are disabled" and
there is no button to enable it.

Attachments:
Screen Shot 2015-06-23 at 9.13.41 AM.png 458 KB

chro...@googlecode.com

unread,
Jul 24, 2015, 1:38:02 PM7/24/15
to chromi...@chromium.org

Comment #28 on issue 468121 by pjo...@visiluna.com: Chrome Remote Desktop
A month since the last comment and I am also experiencing this problem.
Chrome 44.0.2403.107
Mac OS X 10.10.3

Prefs say "Remote connections to this computer are disabled," But there is
no way to enable them. See attached screenshot.

Attachments:
Screen Shot 2015-07-24 at 10.17.20 AM.png 679 KB

chro...@googlecode.com

unread,
Jul 24, 2015, 3:32:43 PM7/24/15
to chromi...@chromium.org

Comment #32 on issue 468121 by Doug.Bag...@gmail.com: Chrome Remote Desktop
I'll see what I can do a little later when I get back home. Does it matter
(to what you need) if Chrome auto updated to version 44 since I last
installed the chromedesktop host patched dmg further up the thread?

chro...@googlecode.com

unread,
Jul 25, 2015, 5:01:06 AM7/25/15
to chromi...@chromium.org

Comment #33 on issue 468121 by bigpoppa...@gmail.com: Chrome Remote Desktop
I am still getting the same issue listed above. As soon as I enable the
computer and the refresh the list it says it is greyed out with a last
online timestamp. I have tried rebooting and logout/login of chrome with
no success.

Chrome 44.0.2403.107 (64bit)
Mac OS X 10.10.3

JS Conslole Logs:
Chrome Remote Desktop version: 44.0.2403.44 (v2)
ui_mode.js:121 App mode: home
host_controller.js:20 Host version: 44.0.2403.25
ui_mode.js:121 App mode: home.host-setup.ask-pin
ui_mode.js:121 App mode: home.host-setup.processing
dns_blackhole_checker.js:165 DNS blackhole check succeeded.
fallback_signal_strategy.js:348 FallbackSignalStrategy progress: xmpp
succeeded
ui_mode.js:121 App mode: home.host-setup.done
ui_mode.js:121 App mode: home

Attachments:
Screen Shot 2015-07-25 at 8.57.36 PM.png 152 KB

chro...@googlecode.com

unread,
Jul 27, 2015, 1:26:36 PM7/27/15
to chromi...@chromium.org

Comment #34 on issue 468121 by jamie...@chromium.org: Chrome Remote
Desktop Host Preferences Can't be "Enabled"
https://code.google.com/p/chromium/issues/detail?id=468121

Is that the entire log? I would expect to see some information on the
version of the host component (which is separate from the Chrome app
version). We recently fixed a server-side bug that meant that the wrong
version of the host component was being served, which might have caused the
problem. Can you try uninstalling them (there should be an "Uninstall
Chrome Remote Desktop" app installed) and try again.

chro...@googlecode.com

unread,
Jul 27, 2015, 11:04:47 PM7/27/15
to chromi...@chromium.org

Comment #35 on issue 468121 by bigpoppa...@gmail.com: Chrome Remote Desktop
Hi, thanks for responding and your help on this.

I ran the uninstall app and re-downloaded and re-installed the chrome
remote desktop host installer. Same issue as before, no change.

Of note, in the app there is a message at the bottom of the "My Computers"
list that says "This computer is shared under a different account." I have
never shared this computer from any other account, but it's always says
that once I run the host installer setup.

There is more data in the log now though, full paste bellow:

Chrome Remote Desktop version: 44.0.2403.44 (v2)
host_daemon_facade.js:213 Native Message port
disconnectedremoting.HostDaemonFacade.onDisconnect_ @
host_daemon_facade.js:213
host_controller.js:27 Host version not available.
ui_mode.js:121 App mode: home
host_daemon_facade.js:213 Native Message port
disconnectedremoting.HostDaemonFacade.onDisconnect_ @
host_daemon_facade.js:213
crd_main.js:130 Pairing registry not supported by host.
host_daemon_facade.js:213 Native Message port
disconnectedremoting.HostDaemonFacade.onDisconnect_ @
host_daemon_facade.js:213
crd_main.js:130 Pairing registry not supported by host.
host_daemon_facade.js:213 Native Message port
disconnectedremoting.HostDaemonFacade.onDisconnect_ @
host_daemon_facade.js:213
ui_mode.js:121 App mode: home.host-install.prompt
host_daemon_facade.js:213 Native Message port
disconnectedremoting.HostDaemonFacade.onDisconnect_ @
host_daemon_facade.js:213
crd_main.js:130 Pairing registry not supported by host.
host_setup_dialog.js:213 Error getting consent status:
ERROR_MISSING_PLUGINonError @ host_setup_dialog.js:213
ui_mode.js:121 App mode: home.host-install.pending
ui_mode.js:121 App mode: home.host-install.prompt
ui_mode.js:121 App mode: home.host-setup.ask-pin
ui_mode.js:121 App mode: home.host-setup.processing
dns_blackhole_checker.js:165 DNS blackhole check succeeded.
fallback_signal_strategy.js:348 FallbackSignalStrategy progress: xmpp
succeeded
ui_mode.js:121 App mode: home.host-setup.done
ui_mode.js:121 App mode: home

chro...@googlecode.com

unread,
Jul 28, 2015, 1:37:43 PM7/28/15
to chromi...@chromium.org

Comment #36 on issue 468121 by jamie...@chromium.org: Chrome Remote
Desktop Host Preferences Can't be "Enabled"
https://code.google.com/p/chromium/issues/detail?id=468121

The "different account" message indicates that the host is enabled, but not
for the *Google account* you're signed into Chrome using. It's not related
to local accounts on your Mac. You might see this if you had previously
enabled connections to this computer using an old version of Chrome Remote
Desktop (when it ran in a browser tab).

Probably the easiest fix is to run the following command:

sudo rm /Library/PrivilegedHelperTools/org.chromium.chromoting.*

Then restart the Chrome Remote Desktop app and try enabling the host again.
If it still doesn't work, please file a separate bug with details of the
repro steps, error messages and log, then follow up with the bug number
here--this is a very old bug now and I suspect that the underlying cause of
what you're seeing is different.

chro...@googlecode.com

unread,
Jul 29, 2015, 6:47:36 AM7/29/15
to chromi...@chromium.org

Comment #37 on issue 468121 by bigpoppa...@gmail.com: Chrome Remote Desktop
No luck. New bug report here: 515032

It came up with a system error log message, pasted bellow is the output
from the system logs. I tried running the uninstaller again and
reinstalled the host, repro the steps and got the same original host
failure.

Jul 29 20:51:30 Bigpoppa-X kernel[0]: Google Chrome He (map:
0xffffff805fa3fc30) triggered DYLD shared region unnest for map:
0xffffff805fa3fc30, region 0x7fff89600000->0x7fff89800000. While not
abnormal for debuggers, this increases system memory footprint until the
target exits.
Jul 29 20:51:33 Bigpoppa-X kernel[0]: Google Chrome He (map:
0xffffff805fa3f870) triggered DYLD shared region unnest for map:
0xffffff805fa3f870, region 0x7fff89600000->0x7fff89800000. While not
abnormal for debuggers, this increases system memory footprint until the
target exits.
Jul 29 20:51:35 Bigpoppa-X kernel[0]: Google Chrome He (map:
0xffffff8069279690) triggered DYLD shared region unnest for map:
0xffffff8069279690, region 0x7fff89600000->0x7fff89800000. While not
abnormal for debuggers, this increases system memory footprint until the
target exits.
Jul 29 20:51:37 Bigpoppa-X kernel[0]: Google Chrome He (map:
0xffffff80679d4e10) triggered DYLD shared region unnest for map:
0xffffff80679d4e10, region 0x7fff89600000->0x7fff89800000. While not
abnormal for debuggers, this increases system memory footprint until the
target exits.
Jul 29 20:51:37 Bigpoppa-X.local native_messaging_host[2368]: icudtl.dat
not found in bundle
Jul 29 20:51:37 Bigpoppa-X kernel[0]: Data/Stack execution not permitted:
Google Chrome He[pid 2369] at virtual address 0x10cd03000, protections were
read-write
Jul 29 20:51:40 Bigpoppa-X.local native_messaging_host[2368]: Failed to
read /Library/PrivilegedHelperTools/org.chromium.chromoting.json
Jul 29 20:52:02 Bigpoppa-X.local System Preferences[2371]:
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing
semicolon in dictionary on line 7. Parsing will be abandoned. Break on
_CFPropertyListMissingSemicolon to debug.
Jul 29 20:52:07 Bigpoppa-X com.apple.xpc.launchd[1]
(com.apple.appkit.xpc.sandboxedServiceRunner): The JoinExistingSession key
is only available to Application services.
Jul 29 20:52:07 Bigpoppa-X com.apple.xpc.launchd[1]
(com.apple.DataDetectorsDynamicData): The JoinExistingSession key is only
available to Application services.
Jul 29 20:52:25 Bigpoppa-X.local authexec[2381]: executing
/Library/PrivilegedHelperTools/org.chromium.chromoting.me2me.sh
Jul 29 20:52:26 Bigpoppa-X.local System Preferences[2371]:
AuthorizationExecuteWithPrivileges: errAuthorizationToolExecuteFailure
(-60031)
Jul 29 20:52:26 Bigpoppa-X.local System Preferences[2371]: Failed to run
the helper tool
Jul 29 20:52:39 Bigpoppa-X.local authexec[2382]: executing
/Library/PrivilegedHelperTools/org.chromium.chromoting.me2me.sh
Jul 29 20:52:39 Bigpoppa-X.local System Preferences[2371]:
AuthorizationExecuteWithPrivileges: errAuthorizationToolExecuteFailure
(-60031)
Jul 29 20:52:39 Bigpoppa-X.local System Preferences[2371]: Failed to run
the helper tool
Reply all
Reply to author
Forward
0 new messages