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

looks like it's 404ing for the .deb. i tried checking to see if there's a new version but either they entirely changed their directory structure or they serve a 404 on a GET to the directory it's in.

How do i enable audio ??

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.

Also, this patch adds an option to use the existing session (but it's disable by default for compatibility reasons).

https://gist.github.com/nightuser/2ec1b91a66ec33ef0a0a67b6c570eb40

To enable it, create ~/.config/chrome-remote-desktop/Xsession file with a proper session number (usually 0 or 1).

Unfortunately, I don't yet know how to transfer sound in this case (it'll probably require enabling public pulseaudio config).

@frealgagu: Please, use the direct links to the versioned packages instead of the latest one. Fixed PKGBUILD: https://gist.github.com/nightuser/bb6aab68010a4c53e0537cfb7d7e965b ).

They have the following format:

"https://dl.google.com/linux/${pkgname}/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_amd64.deb"

Maybe we should run

/opt/google/chrome-remote-desktop/chrome-remote-desktop --size="${crd_size}" --start

with exec?

Also, the checksum changed again.

My issue was fixed: I also needed to uncomment the DBUS line in the .chrome-remote-desktop-session file. However, the systemd service does not work. It times out after a couple of minutes:

mar 13 19:35:55 sofia-pc systemd[831]: chrome-remote-desktop.service: Failed with result 'timeout'.
mar 13 19:35:55 sofia-pc systemd[831]: Failed to start "Chrome Remote Desktop host daemon".

Funny thing, while it is still working, CRD works fine, and it also works fine if I manually issue crd --start. Any idea?

It seems I can't get this working, neither with the online nor with the headless installation modes. The package builds fine, but when I try to start crd the session cannot start:

Launching X server and X session.
Starting Xvfb on display :20
X server is active.
Launching X session: ['/bin/sh', '/home/cestino/.chrome-remote-desktop-session']
Launching host process
['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/cestino/.config/chrome-remote-desktop/pulseaudio#2293cd462a/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.cestino.ssh_auth_sock', '--signal-parent']
wait() returned (397849,256)
Session process terminated
Failure count for 'session' is now 1
Terminating X server
Terminating host
Failure count for 'X server' is now 0
Failure count for 'host' is now 0
Waiting before relaunching
wait() returned (397848,256)
Waiting before relaunching

I use KDE and configured CRD to start using startplasma-x11, as it should be. Any idea on how to proceed?

@ansonx10 you're right, it's the way Windows and MAC behave. I don't want to affect users who have already installed, therefore, if most users prefer to have the current session, I will make the change. I want to know if there are reasons to use a different session instead of the current one.

@frealgagu Well Chrome Remote Desktop users that come from other platforms, i.e. Windows and Mac, would expect it to behave the same way on Linux. (It lets you control your existing "session" on Windows and macOS) It would be more useful for me to be able to control my existing session by default. I can't personally think of a reason that I'd need to access my own computer in a new session, and in fact, creating a new session can cause problems for some software. Using VNC is always an option regardless, but the simplicity of remote connections in CRD is nice. In the spirit of simplicity (with the target demographic in mind), I'd advocate for current session being the default.