Package Details: chrome-remote-desktop 83.0.4103.2-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: 111
Popularity: 2.05
First Submitted: 2014-04-27 23:43
Last Updated: 2020-04-16 23:06

Pinned Comments

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

jamesan commented on 2014-08-16 09:59

I get the same error as muhas both when starting the systemd service unit and when starting it manually (/opt/google/chrome-remote-desktop/chrome-remote-desktop --start) while using SLiM/XFCE4. Not sure how to get passed this... I might test this on GDM/GNOME 3 if I get the time.

Anonymous comment on 2014-08-15 17:21

Unfortunately I have yet to find any way to track whenever there is a new update. So, if you ever get a md5sum mismatch, you should do this:
Open the deb and check if the control file inside control.tar.gz shows a different version. If so, just flag as out of date.
If the version is correct, just comment here that the md5sums are wrong for some reason.

I added two conditions to the service, now you should only be able to run it if ~/.config/chrome-remote-desktop is non-empty and there's a host#*.json file inside of it.

If you have ever any problems unrelated to the packaging, just file a bug at and link it here so other affected users can star it. Also, remember to link here from the bug report so the devs can confirm it really isn't a packaging error.

vendion commented on 2014-08-14 10:45

Did anyone need to create a "$HOME/.chrome-remote-desktop-session" file like the setup directions states ( This still isn't working for me and not sure if it is caused by my Login Manager (SLiM) or my window manager (Wingo).

silverhammermba commented on 2014-08-14 02:22

I had no problems getting this to work. After installing the package

1. mkdir ~/.config/chrome-remote-desktop
2. Run app and enable remote connections
3. Enable user service

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!