Package Details: chrome-remote-desktop 77.0.3865.32-1

Git Clone URL: (read-only)
Package Base: chrome-remote-desktop
Description: Access other computers or allow another user to access your computer securely over the Internet
Upstream URL:
Keywords: Chrome Chromium Google Networking Remote
Licenses: BSD
Submitter: None
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 104
Popularity: 2.873979
First Submitted: 2014-04-27 23:43
Last Updated: 2019-08-27 15:50

Pinned Comments

frealgagu commented on 2019-08-12 22:41

@apepa you still need to download and install a package (.deb). This package downloads and converts to pacman for archlinux installation. Please don't flag this as outdated because is not.

Latest Comments

« First ‹ Previous ... 16 17 18 19 20 21

sacarde commented on 2014-07-09 09:45

I dont view "chrome-remote-desktop" in "systemctl list-unit-files"
is this OK ?


dlh commented on 2014-06-30 06:32

Please update pkg to create symlink.

Anonymous comment on 2014-06-25 20:05

Grr, I still don't get when the hell that host json file is created. Maybe creating the hashes is important for it?
Also, I tried creating a systemd service for it, currently it will run in user mode, I still have to test it when I manage to create that host file.
Also, about the chromium issue: You should have a symbolic link so that /etc/chromium/native-messaging-hosts redirects to /etc/opt/chrome/native-messaging-hosts. I have already created this on the next pkgrel.

jamesan commented on 2014-06-23 08:52

Package builds and installs without a hitch. It works only for one-time remote access and only with the CRD extension installed on Chrome.

CRD installed on Chromium doesn't seem to detect that this package is installed (so doesn't execute the binaries and generate the one-time access code).

Also, CRD doesn't allow for the user's DE to be registered under the persistent remoting list, probably because the host process isn't running (persistently under a service unit). Running /opt/google/chrome-remote-desktop/chrome-remote-desktop --start manually halts when it can't find the ~/.config/chrome-remote-desktop/host#SOME_HASH.json file. I can't figure out how this JSON file is created...

The Feb 21, 2014 comment at: seems to imply that running chrome-remote-desktop --start simply works (and the JSON file is automagically generated) and provides a systemd service unit file template.

Has any passed where I'm stuck here?

Anonymous comment on 2014-06-07 17:48

Patched the python script so it uses Python 2 instead of Python 3 and pkexec instead of gksudo.
I'll wait until they port to Fedora to provide the init service:

dlh commented on 2014-06-07 12:47

Doesn't work