Package Details: chrome-remote-desktop 87.0.4280.51-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: 114
Popularity: 0.89
First Submitted: 2014-04-27 23:43
Last Updated: 2020-11-14 06:44

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 ... 7 8 9 10 11 12 13 14 15 16 17 ... Next › Last »

DaveB commented on 2017-09-19 13:45

Thanks :)

There shouldn't be a resource difference since either method does much the same thing, but autostarting using systemd may run some single-instance programs in the CRD session that you'd want to use in your native desktop session.

annoyingduck commented on 2017-09-19 02:30

Bravo on this package, makes installing a breeze. 2 questions: is there a big resource difference between autostarting via systemctl --user enable chrome-remote-desktop.service or adding crd to the startup applications? 2nd: on Windows there is a clear notification that the desktop is being accessed/actions can be seen on the target computer screen, but not on Linux (there is zero indication that another computer is accessing the target machine). Anyone come up with a way to tell if your computer is being accessed via crd?

DaveB commented on 2017-06-02 21:00

Done. What a messy update. Thanks for alpha and beta testing, spider-mario and Zeroedout.

spider-mario commented on 2017-06-01 21:57

Also, I think the new line:
echo "export $(dbus-launch)" >> ...

should use single quotes, not double quotes.

Zeroedout commented on 2017-06-01 17:58

MD5sum failed on crd.
crd ... FAILED

kokeroulis commented on 2017-05-26 18:43

I am trying to install the crd and i am seeing the following error,

does anyone know how i can fix this?

The package xorg-xrandr is installed and the version is 1.5.0-1

DaveB commented on 2017-05-23 07:58

PSA: Chrome Remote Desktop is not part of the Google Chrome package. The CRD versions lag behind.

Kuchiriel commented on 2017-05-09 04:48

Someone please create an openrc package of this!

DaveB commented on 2017-04-11 10:27

Thanks @Bittersourness!

Bittersourness commented on 2017-04-11 09:17

If anyone is having trouble with dbus and KDE with a message like this (FYI @grayjoc):

dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
startkde: Could not sync environment to dbus.

You have to add "export $(dbus-launch)" before startkde in ~/.chrome-remote-desktop-session:

# You will have to uncomment one of the following lines for CRD to work
# Remove the # and select ctrl-X to finish.
export $(dbus-launch)
exec /usr/bin/startkde
# exec /usr/bin/openbox-session
# exec /usr/bin/openbox-kde-session

And that's it, you will see your desktop like a boss! :D