Package Details: chrome-remote-desktop 85.0.4183.39-1

Git Clone URL: (read-only, click to copy)
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: 113
Popularity: 1.69
First Submitted: 2014-04-27 23:43
Last Updated: 2020-07-28 05:00

Pinned Comments

victorbrca commented on 2020-04-03 01:04

Thanks @frealgagu for packaging this, @nightuser for the existing session patch and @Brinsky for the instructions.

I've compiled both instructions with screenshots and added it to my blog if anyone is having issues with the install. Otherwise, just follow the instructions in the comments by @Brinsky from 2019-12-06 13:58.

Brinsky commented on 2019-12-06 13:58

Here's how I got this working with the new web app (

  1. Build and install the package
  2. run crd --setup
  3. (Optional) Configure execution of your preferred window manager in ~/.chrome-remote-desktop-session
  4. Go to
  5. Click "next" and "authorize" through each instruction
  6. Copy/paste and run the provided "Debian" command, which should look like the following: DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="<UNIQUE_CODE>" --redirect-url="<>" --name=
  7. Set up a name and PIN
  8. Wait for successful output containing "Host ready to receive connections."
  9. Run crd --start

Latest Comments

« First ‹ Previous ... 20 21 22 23 24 25

Anonymous comment on 2014-07-09 16:18

@sacarde It's a user service, you need to use systemd on user mode (--user) to start it.
Try "systemctl --user list-unit-files" and "systemctl enable chrome-remote-desktop.service" as your own user.

sacarde commented on 2014-07-09 15:49

if I try:

systemctl enable chrome-remote-desktop.service

Failed to execute operation: No such file or directory

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