Arch Linux User Repository

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.chrome-remote-desktop/releases/

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.

Here's how I got this working with the new web app (remotedesktop.google.com):

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 http://remotedesktop.google.com/headless
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="<https://remotedesktop.google.com/_/oauthredirect>" --name=
7. Set up a name and PIN
8. Wait for successful output containing "Host ready to receive connections."
9. Run crd --start

I also see:

==> Validating source files with sha256sums... chrome-remote-desktop-71.0.3578.31.deb ... FAILED

I'm more familiar with GitHub regarding sending a pull-request; I understand it's not great having to maintain frequent changes.

I ran into similar errors as other comments with not being able to connect after entering a PIN. In looking into log files I could see errors for :20 display. This appeared to be fixed by pacman -S xorg-xrandr. This got me partway - the Manjaro device showed 'started', but the only thing showing up in clients was an error due to 'Unable to contact settings server'. I discovered that contrary to the comment in ~/.chrome-remote-desktop-session I needed to uncomment both lines, so that I had:

export $(dbus-launch)
exec startxfce4

I was then able to see the Manjaro desktop on the remote client.

@mradi have you found the way to use it in :0 display ?

==> Validating source files with sha256sums... chrome-remote-desktop-71.0.3578.31.deb ... FAILED

Looks like the sha256sums are different.

I think it need the xorg-xrandr as dependency

Is there way to have CRD use the same xsession that's currently running instead of spinning up a new one?

I updated my graphics card to nvidia, and updated GDM, gnome. I followed the post to use display :0 as my chrome-remote-desktop and it worked fine. but when I recently tried it, again I started seeing errors like this, can someone help

2018-09-08 23:47:04,227:INFO:Using host_id: 529e63f8-0684-5932-d0a4-5bfa5866cf66
2018-09-08 23:47:04,228:INFO:Launching X server and X session.
2018-09-08 23:47:04,244:INFO:X server is active.
2018-09-08 23:47:04,623:INFO:Launching X session: ['/bin/sh', '/home/xyz/.chrome-remote-desktop-session']
2018-09-08 23:47:04,625:INFO:Launching host process
2018-09-08 23:47:04,625:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/xyz/.config/chrome-remote-desktop/pulseaudio#20383fe03b/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.xyz.ssh_auth_sock', '--signal-parent']
2018-09-08 23:47:04,627:INFO:wait() returned (6740,0)
2018-09-08 23:47:04,627:INFO:Session process terminated
2018-09-08 23:47:04,640:INFO:Failure count for 'session' is now 1
2018-09-08 23:47:04,640:INFO:Terminating host
2018-09-08 23:47:04,641:INFO:Failure count for 'X server' is now 0
2018-09-08 23:47:04,641:INFO:Failure count for 'host' is now 0
2018-09-08 23:47:04,641:INFO:Waiting before relaunching
2018-09-08 23:47:06,643:INFO:wait() returned (6739,0)
2018-09-08 23:47:06,644:INFO:Waiting before relaunching
2018-09-08 23:47:09,630:INFO:Launching X server and X session.
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 1685
2018-09-08 23:47:09,648:INFO:X server is active.
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 534
2018-09-08 23:47:09,798:INFO:Launching X session: ['/bin/sh', '/home/xyz/.chrome-remote-desktop-session']
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 705
2018-09-08 23:47:09,800:INFO:Launching host process
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 1692
2018-09-08 23:47:09,800:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/xyz/.config/chrome-remote-desktop/pulseaudio#20383fe03b/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.xyz.ssh_auth_sock', '--signal-parent']

systemctl --user start chrome-remote-desktop gets me this:

Jul 22 15:33:18 nwkr-desktop crd[762]: OAuth credentials are invalid - exiting.

Still, clicking "Enable remote connections" in CRD App works totally fine.

What went wrong?

Please, use version for package filename:

https://github.com/Jguer/yay/issues/523#issuecomment-401761706