Skip to content

Instantly share code, notes, and snippets.

@wjt

wjt/NOTES.md

Created October 1, 2020 13:49
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save wjt/5bcfb122bb36008c7f604f692e1b314f to your computer and use it in GitHub Desktop.
Save wjt/5bcfb122bb36008c7f604f692e1b314f to your computer and use it in GitHub Desktop.
Download ZIP
Chrome Remote Desktop on Endless OS 3.8 and Fedora 32
Raw
NOTES.md

I tried to make Chrome Remote Desktop work on Endless OS 3.8 and Fedora 32, with varying degrees of failure.

Endless OS

The chrome-remote-desktop.deb package that is downloaded by the installation process depends on python3-psutil (in our repo), some other X11 thing (in our repo), and x11-session-utils which is not in our repo.

I did the following:

  • eos-dev-unlock
  • configuring the Endless APT repos which are only available to Endless employees
  • Installed x11-session-utils from Debian
  • Installed other dependencies from the Endless APT repo (perhaps the Debian Bullseye versions would also have worked)
  • Installed chrome-remote-desktop.deb

Now, I am not able to use the "remote access" feature at https://remotedesktop.google.com/access which allows logging in a new session, but I am able to use the "Remote Support" tab to generate a code, which I entered into Firefox on another machine and was able to drive my desktop remotely.

Fedora 32

Google only serves up a chrome-remote-desktop.deb, not an .rpm. There is a chrome-remote-desktop package in the Fedora repositories, which Tom Callaway, RH's Chromium maintainer, says is there precisely because Google only provides a .deb.

I tried:

  • Installed chrome-remote-desktop
  • Installed chromium
  • Installed python3-psutil
  • Browsing to <remotedesktop.google.com> in Chromium and opting to install the extension

Problems:

  • The web interface waits forever for me to install the .deb package. I can't work out what is supposed to call back to it to say that the native component is installed.
  • /usr/lib64/chrome-remote-desktop/chrome-remote-desktop and /etc/chromium/native-messaging-hosts/chrome-remote-desktop and /etc/opt/chrome/native-messaging-hosts/chrome-remote-desktop (all the same file) have a #!/usr/bin/python2 shebang but use Python 3 syntax. (Easily fixed in a text editor.)
  • abrt popped up to say that remote-assistance-host had been killed by SIGABRT
  • After fixing the shebang, systemctl status chrome-remote-desktop@wjt.service exits immediately.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment