Package Details: chrome-remote-desktop 84.0.4147.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: 112
Popularity: 1.36
First Submitted: 2014-04-27 23:43
Last Updated: 2020-06-26 18:04

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

delin commented on 2014-08-07 18:54

Additional, need to:
sudo mkdir /etc/chrome-remote-desktop-session
systemctl --user enable chrome-remote-desktop.service
systemctl --user start chrome-remote-desktop.service

but, on connect:
[30935.930103] ChromotingNetwo[4523]: segfault at e0 ip 00000000004e676d sp 00007f3f91c03320 error 4 in chrome-remote-desktop-host[400000+5e4000]

muhas commented on 2014-08-01 06:36

systemctl start chrome-remote-desktop.service
Failed to start chrome-remote-desktop.service: Unit chrome-remote-desktop.service failed to load: No such file or directory.

/opt/google/chrome-remote-desktop/chrome-remote-desktop --start
2014-08-01 10:34:13,158:INFO:Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20140801_103413_ACW0AG'
Using host_id: eb4a9968-0a7c-1cdc-b0b5-2effb06d740d
Launching X server and X session.
Log file: cat /tmp/chrome_remote_desktop_20140801_103413_ACW0AG

Exception IOError: (9, 'Bad file descriptor') in <bound method _TemporaryFileWrapper.__del__ of <closed file '<fdopen>', mode 'w+b' at 0x7ff9f2283780>> ignored
2014-08-01 10:34:13,159:INFO:Using host_id: eb4a9968-0a7c-1cdc-b0b5-2effb06d740d
2014-08-01 10:34:13,160:INFO:Launching X server and X session.
Traceback (most recent call last):
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1243, in <module>
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1170, in main
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 471, in launch_session
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 369, in _launch_x_server
if (len(x_session) == 2 and
TypeError: object of type 'NoneType' has no len()
2014-08-01 10:34:13,178:INFO:Cleanup

vendion commented on 2014-07-22 02:27

@CharlesAtum even without the service running when I Enable Remote Connections from the chrome app I get: "Failed to start remote access service" See

I may not have my .chrome-remote-desktop-session file right, that or it doesn't like something about my setup (SLiM for login manager and Wingo for WM).

Anonymous comment on 2014-07-21 14:14

@vendion You should run the Chrome Remote Desktop app first and Enable Remote Connections there. After that the service can be run.
Also, I may add the "ConditionDirectoryNotEmpty" condition on a future pkgrel.

vendion commented on 2014-07-21 11:09

The SystemD service seems like it is unable to load for me. I created the "~/.config/chrome-remote-desktop" enabled and started the service it fails with:

Jul 21 07:04:27 Baldr systemd[823]: Starting "Chrome Remote Desktop host daemon"...
Jul 21 07:04:27 Baldr chrome-remote-desktop[3530]: Failed to load config: [Errno 2] No such file or directory: '/home/vendion/.config/chrome-remote-desktop/host#d20b60e1d094abcbd6a458593874c8ed.json'
Jul 21 07:04:27 Baldr chrome-remote-desktop[3530]: 2014-07-21 07:04:27,185:INFO:Cleanup.
Jul 21 07:04:27 Baldr systemd[823]: chrome-remote-desktop.service: control process exited, code=exited status=1
Jul 21 07:04:27 Baldr systemd[823]: Failed to start "Chrome Remote Desktop host daemon".
Jul 21 07:04:27 Baldr systemd[823]: Unit chrome-remote-desktop.service entered failed state.

Infact the chrome-remote-desktop directory is empty. Anyone run into something like this, because the services fails to load I can't configure remote destktop?

phazen18 commented on 2014-07-21 00:03

This is starting to look like its getting in pretty good shape. For the first time, I can enable the plugin on the host side and start a session on the client side. However, it looks like its getting a broken xterm session of some kind then terminates. FWIW, I'm on Gnome.

Thanks for all the effort so far. I can't wait for this to work!

Anonymous comment on 2014-07-18 00:19

The devs made the python script compatible with both psutil versions, so I dropped the patch and got back to using sed for python 2 and pkexec support.
I made some changes in the systemd service, remember that you can override it anytime at in ~/.config/systemd/user/ for your user or /etc/systemd/user/ for all users.
The install script gives some more info, sorry if it's somehow annoying.

ava1ar commented on 2014-07-16 20:17


Looks like connection is established, but creation session on linux side is not working. I will try to troubleshot it on VM and will post update later on. Thanks for sharing you experience.

thepasto commented on 2014-07-13 10:44

@ava1ar thanks for your work!

here's my try. Everything seems to work as well. I can enable incoming connection on my laptop, but when i try to access from my tablet i get this error.

ava1ar commented on 2014-07-10 05:54

Few more notes:

I created a patch for python2-psutils and pkexec compatibility:
Here is updated PKBDUILD, which applies this patch:
It uses following chrome-remote-desktop.install file:

Install file required to request manual action: user should create ~/.config/chrome-remote-desktop folder manually after installation, otherwise chrome plugin won't allow to setup access.

After all this action I was able to setup the access, but I failed to check it, since it currently supports only gdm/lightdm setup, but I ma using KDE. So fill free to try and share you experience!