The problem happens even if I run crd --start
after a reboot.
(note I did not systemctl enable --user chrome-remote-desktop.service)
I might be wrong, but I think this line in the log suggests that it actually successfully started the X server:
INFO:X server is active.
I'm suggesting that xorg-xrandr
as a dependency because it seems to be using xrandr
to test whether resizing is supported. Line 563 crashes with
OSError: [Errno 2] No such file or directory
if the executable does not exist.
/opt/google/chrome-remote-desktop/chrome-remote-desktop
540 def _launch_xvfb(self, display, x_auth_file, extra_x_args):
562 with open(os.devnull, "r+") as devnull:
563 exit_code = subprocess.call("xrandr", env=self.child_env,
564 stdout=devnull, stderr=devnull)
565 if exit_code == 0:
566 # RandR is supported
567 self.server_supports_exact_resize = True
568 self.server_supports_randr = True
569 self.randr_add_sizes = True
Pinned Comments
frealgagu commented on 2020-12-05 22:38 (UTC)
I maintain the latest built package at:
https://github.com/frealgagu/archlinux.chrome-remote-desktop/releases/
victorbrca commented on 2020-04-03 01:04 (UTC)
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.
Brinsky commented on 2019-12-06 13:58 (UTC)
Here's how I got this working with the new web app (remotedesktop.google.com):
crd --setup
~/.chrome-remote-desktop-session
DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="<UNIQUE_CODE>" --redirect-url="<https://remotedesktop.google.com/_/oauthredirect>" --name=
crd --start