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

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.

@Bakasura It's nice but I'm not sure what is the expected behavior for most users. Do you think you want to use always the active session or you want to open a new session instead? I think chrome-remote-desktop developers use the :20 in order to not affect the current session

@Bakasura nice!

@Terence I created a patch file https://pastebin.com/tjWkgMqq

@frealgagu can you add?

Unable to install due to: Validating source files with sha256sums...chrome-remote-desktop-79.0.3945.10.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build chrome-remote-desktop

Any help with this? I've read the other comments that say this but I'm new and don't understand what is happening. I install Manjaro for the first time yesterday. Thanks for any help!!

@Brinsky It works, thanks a lot.

/usr/bin/crd launches nano. I suggest that either nano be made a dependency for this package or crd be patched to use the $EDITOR variable and check for the $EDITOR's existence before running it.

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