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

After following @brinsky 's comment, It seems like audio comes out from my host machine only. Anyone having the same issue?

@frealgagu @brinsky 's comment should be pinned https://aur.archlinux.org/packages/chrome-remote-desktop/?O=20&PP=10#comment-719586 it's essential for getting CRD to work

@nightuser that's awesome thanks for that!

However I can't seem to get that working it doesn't seem to be picking up that Xsession file in /chrome-remote-desktop/. Do I just copy and paste into the Xsession file that I created and remove the + and - signs? I tried it with the + and - signs as well.

Sorry for the noob questions.

@nightuser ah that's awesome thanks!!

I was still having issues getting it working so I blew away my config and package and re-installed but now I'm getting that it can't read my .json config. So now I'm back at square one lol.

@snipes040 Display 20 is the correct behavior. CRD on Linux starts a new Xorg session instead of the existing one. If you still want to use display 0, see my patch below. It's a bit dirty and doesn't support sound forwarding yet, but, if anyone's interested, I may rewrite it slightly and add the missing features.

Anybody having issues getting this working after updating chrome?

My chrome version is 81.0.4044.122. I see that it's trying to use display number 20 which isn't correct but I changed the display number to 0 and it still fails.

This is what shows up in my log file.

[0423/085635.588957:INFO:host_config_upgrader.cc(125)] Requesting token exchange. [0423/085635.685608:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing. [0423/085635.806379:INFO:host_config_upgrader.cc(148)] No exchange needed, writing new config to mark as upgraded. [0423/085635.815692:INFO:host_config_upgrader.cc(191)] Successfully written host config. 2020-04-23 08:56:35,818:INFO:Using host_id: b56e140d-e5f4-118a-f566-204d28327e9c 2020-04-23 08:56:35,818:INFO:Launching X server and X session. 2020-04-23 08:56:35,826:INFO:Starting Xvfb on display :20 xdpyinfo: unable to open display ":20". The XKEYBOARD keymap compiler (xkbcomp) reports:

Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server 2020-04-23 08:56:36,334:INFO:X server is active. The XKEYBOARD keymap compiler (xkbcomp) reports: Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server 2020-04-23 08:56:36,387:INFO:Launching X session: ['/bin/sh', '/home/snipes/.chrome-remote-desktop-session'] 2020-04-23 08:56:36,389:INFO:Launching host process 2020-04-23 08:56:36,389:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/snipes/.config/chrome-remote-desktop/pulseaudio#3b58159e54/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.snipes.ssh_auth_sock', '--signal-parent'] Session output: /home/snipes/.chrome-remote-desktop-session: line 5: /usr/bin/startkde: No such file or directory 2020-04-23 08:56:36,398:INFO:wait() returned (15630,32512) 2020-04-23 08:56:36,398:INFO:Session process terminated [0423/085636.400338:INFO:remoting_me2me_host.cc(1696)] Starting host process: version 83.0.4103.2 2020-04-23 08:56:36,402:INFO:Failure count for 'session' is now 1 2020-04-23 08:56:36,402:INFO:Terminating X server Gdk-Message: 08:56:36.402: chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20.

So, since Google deletes old versions of the package, we can use pkgver function to generate version from the deb file.

Here's a working PKGBUILD: https://gist.github.com/nightuser/bb6aab68010a4c53e0537cfb7d7e965b

UPD: this works as a VCS package: the version is taken from pkgver() function and then the variable pkgver is overwritten by the returned value.

They host only the latest version of the package. To know which one is the latest: curl -q https://dl.google.com/linux/chrome-remote-desktop/deb/dists/stable/main/binary-amd64/Packages | grep ^Filename. This is taken from Gentoo's PKGBUILD for chrome-remote-desktop package.

@sanerb They didn't change it. The latest URL looks like https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_83.0.4103.2_amd64.deb