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

@zhtlancer is right. I have solved daemon start by creating a file chrome-remote-desktop with that content in /etc/pam.d/

Thank you very much.

hi all, I have a similar problem as osjacky430

on "crd --restart" I get:

The daemon is not currently running [0511/180613.232155:INFO:remoting_user_session.cc(691)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190511_180613_NJ17ss' [0511/180613.232976:WARNING:remoting_user_session.cc(613)] Failed to read from message pipe. Please check log to determine host status.

it looks like no matter what I try to start the service CRD status is always "stopped".

Hi, I can't get the crd to enable remote connection, connect to others or share this computer by enter the code do work, but when I pressed enable remote connection, and enter the PIN number, my computer's name do show up in the list, but just appear to be offline.

Also,

crd --start gives me `[0328/210609.180501:INFO:remoting_user_session.cc(691)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190328_210609_g6ApDa' WARNING:remoting_user_session.cc(613)] Failed to read from message pipe. Please check log to determine host status.

Log file: /tmp/chrome_remote_desktop_20190328_210609_g6ApDa`

But I got permission denied FATAL:remoting_user_session.cc(262)] [PAM] Account check: Authentication failure

I've done what @zhtlancer said, but the issue still persists.

If anyone wants to use the current xsession (display: 0) you can follow the answer here https://superuser.com/questions/778028/configuring-chrome-remote-desktop-with-ubuntu-gnome-14-04/850359#850359 (from MDMower) I also had to add an extra pam rule to get it working, like @zhtlancer said

Recent update of PAM subsystem caused failing start of chrome-remote-desktop on my system. Add an extra pam rule for chrome-remote-desktop fixed it. This should be included in the package. Create "/etc/pam.d/chrome-remote-desktop" with following content:

auth        required    pam_unix.so
account     required    pam_unix.so
password    required    pam_unix.so
session     required    pam_unix.so

This package works fine on machines where I've already set up sharing. However, the web app won't let me share from new machines. It keeps prompting me to install the host package and having me download the .deb file, even through I have already installed this package from AUR.

How do I convince the web app that I have installed this already so that it can generate a host#...json file for me? (Really frustrating that I have to go through this clunky web app just to generate a single file, but that's how Google seems to have designed it.)

systemctl --user enable chrome-remote-desktop
Failed to connect to bus: Нет такого файла или каталога

I need help.

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 ?