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

Is using headless mandatory for it to work? It kind of creates a parallel user session which has restrictions when it comes to file and app access.

I am a newbie with Linux and I just wanted to share my experience how I made it work with my Mac, maybe someone has the same issue as I had.

I managed to register my Arch PC in my Mac's chrome remote desktop's list with Brinsky's comment, but it was offline, even tho the service was running on Arch. So I added these lines in the ~/.chrome-remote-desktop-session file:

if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
  eval "$(dbus-launch --sh-syntax)"
  export DBUS_SESSION_BUS_ADDRESS
  export DBUS_SESSION_BUS_PID
fi

export XDG_CURRENT_DESKTOP=GNOME
export DESKTOP_SESSION=gnome
export GNOME_SHELL_SESSION_MODE=classic
export DISPLAY=:20
export GDK_BACKEND=x11
export XDG_SESSION_TYPE=x11

exec /usr/bin/gnome-session --session=gnome

I use GNOME, so those values should be changed for you, if you use something else. But since it's a virtual desktop session you can technically use anything as long as it's installed.

But this won't change the fact that this still starts a new virtual desktop session and your actual session is not reachable.

I'm running on a steam deck and I managed to get this to work following Brinsky's pinned instructions.

My main issue though is I'm not quite getting the desired behavior. When I connect from chrome remote on another computer I can take control of my steam deck, but the problem is I'm getting a new session and not taking over the running session on my steam deck. I leave open windows and ongoing tasks on my deck and I want to remote-in and continue them when I'm not at home, not launch new windows which wont be running when I get home. This is the behavior I get when I use chrome to control my windows PCs.

Is there some alteration I can make to the lines executing preferred window manager in the .chrome-remote-desktop-session file that will achieve this? I have tried both the default options with no success.

Many thanks for a great piece of work guys! Best, Chris

P.s. An aside for any people having trouble with the provided instructions (Brinsky's pinned comment)...

Step 1. Build and install the package, actually means, run the following commands...

git clone https://aur.archlinux.org/chrome-remote-desktop.git
makepkg -si (whilst in the folder the git repo was cloned to)

and Step 3. (Optional), is not optional at all, it absolutely must be done, you need to edit that file and un-rem one of the preferred window manager options.

i can't get any further then: Display= /opt/google/chrome-remote-desktop/start-host....

=> No such file or directory

i am on a steam deck tho.. but i've seen people have it running

Changing locally the version to 128.0.6613.44 then executing command makepkg -si --skipchecksums installs the package successfully.

After running the instruction from @Brinsky post I get an error related to missing .json file in /home/<username>/.config/chrome-remote-desktop/host#*.json. I fixed it by manually adding my user to chrome-remote-desktop group usermod -aG chrome-remote-desktop <USER>

After I restarted the chrome-remote-desktop service with systemctl --user restart chrome-remote-desktop I get the following error:

Sep 18 10:31:38 <HOST> systemd[1469]: Starting "Chrome Remote Desktop host daemon"...
Sep 18 10:31:38 <HOST> crd[276834]: /opt/google/chrome-remote-desktop/chrome-remote-desktop:2529: SyntaxWarning: invalid escape sequence '\s'
Sep 18 10:31:38 <HOST> crd[276834]:   re.split('\s+', os.environ[HOST_EXTRA_PARAMS_ENV_VAR].strip())
Sep 18 10:31:41 <HOST> pkexec[276835]: pam_unix(polkit-1:session): session opened for user root(uid=0) by sitram(uid=1000)
Sep 18 10:31:42 <HOST> crd[276914]: /opt/google/chrome-remote-desktop/chrome-remote-desktop:2529: SyntaxWarning: invalid escape sequence '\s'
Sep 18 10:31:42 <HOST> crd[276914]:   re.split('\s+', os.environ[HOST_EXTRA_PARAMS_ENV_VAR].strip())
Sep 18 10:31:42 <HOST> crd[276914]: Killing process 276908
Sep 18 10:31:42 <HOST> systemd[1469]: Started "Chrome Remote Desktop host daemon".

I might be an issue related to the python version installed based on what I researched online. When I run python -V I saw I have installed version 3.12.6

I replaced the \s with \\s in /opt/google/chrome-remote-desktop/chrome-remote-desktop

2562: extra_start_host_args = []
2527:  if HOST_EXTRA_PARAMS_ENV_VAR in os.environ:
2528:      extra_start_host_args = \
2529:          re.split('\\s+', os.environ[HOST_EXTRA_PARAMS_ENV_VAR].strip())

After restarting the chrome--remote-desktop service, the status showed that the daemon is successfully started

systemctl --user status chrome-remote-desktop.service
○ chrome-remote-desktop.service - "Chrome Remote Desktop host daemon"
     Loaded: loaded (/usr/lib/systemd/user/chrome-remote-desktop.service; enabled; preset: enabled)
     Active: inactive (dead) since Wed 2024-09-18 10:40:11 EEST; 3s ago
 Invocation: b1f776d453fa4b2aaf5cab4acbb8f3ab
    Process: 285042 ExecStart=/usr/bin/crd --start (code=exited, status=0/SUCCESS)
    Process: 285118 ExecStop=/usr/bin/crd --stop (code=exited, status=0/SUCCESS)
   Mem peak: 16.3M
        CPU: 332ms

Sep 18 10:40:08 <HOST> systemd[1469]: Starting "Chrome Remote Desktop host daemon"...
Sep 18 10:40:11 <HOST> pkexec[285047]: pam_unix(polkit-1:session): session opened for user root(uid=0) by sitram(uid=1000)
Sep 18 10:40:11 <HOST> crd[285122]: Killing process 285116
Sep 18 10:40:11 <HOST> systemd[1469]: Started "Chrome Remote Desktop host daemon".

It is not about what I prefer. It's about what it (mis)represents. I get what you are trying to do, but this is not how it's done. You should try to work with @frealgagu and get chrome-remote-desktop updated. If he does not respond in reasonable time, and the package is not maintained, you should create orphan request and then adopt the package if accepted.

And to the PKGBUILD itself, having SKIP for the sha256sum check of the .deb file itself is WRONG and should not be done!

@jvybihal I could change it to -latest if you prefer. Or merge it like you suggested :)

How is this -git package??