Package Details: chrome-remote-desktop 83.0.4103.2-1

Git Clone URL: https://aur.archlinux.org/chrome-remote-desktop.git (read-only, click to copy)
Package Base: chrome-remote-desktop
Description: Access other computers or allow another user to access your computer securely over the Internet
Upstream URL: https://remotedesktop.google.com
Keywords: Chrome Chromium Google Networking Remote
Licenses: BSD
Submitter: None
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 111
Popularity: 2.14
First Submitted: 2014-04-27 23:43
Last Updated: 2020-04-16 23:06

Pinned Comments

Brinsky commented on 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

Anonymous comment on 2014-07-18 00:19

The devs made the python script compatible with both psutil versions, so I dropped the patch and got back to using sed for python 2 and pkexec support.
I made some changes in the systemd service, remember that you can override it anytime at in ~/.config/systemd/user/ for your user or /etc/systemd/user/ for all users.
The install script gives some more info, sorry if it's somehow annoying.

ava1ar commented on 2014-07-16 20:17

@thepasto

Looks like connection is established, but creation session on linux side is not working. I will try to troubleshot it on VM and will post update later on. Thanks for sharing you experience.

thepasto commented on 2014-07-13 10:44

@ava1ar thanks for your work!

here's my try. Everything seems to work as well. I can enable incoming connection on my laptop, but when i try to access from my tablet i get this error.
https://drive.google.com/file/d/0B-yQDH0HYifnMXlMbG00cWk4Q3M/edit?usp=sharing

ava1ar commented on 2014-07-10 05:54

Few more notes:

I created a patch for python2-psutils and pkexec compatibility: http://pastebin.com/JtmP5kDk
Here is updated PKBDUILD, which applies this patch: http://pastebin.com/bFpb8eP8
It uses following chrome-remote-desktop.install file: http://pastebin.com/266042tB

Install file required to request manual action: user should create ~/.config/chrome-remote-desktop folder manually after installation, otherwise chrome plugin won't allow to setup access.

After all this action I was able to setup the access, but I failed to check it, since it currently supports only gdm/lightdm setup, but I ma using KDE. So fill free to try and share you experience!

ava1ar commented on 2014-07-10 05:18

Few more notes:
- simple replacement gksudo with pkexec as done currently will not work. I am kdeuser, so I installed kdesudo from AUR and made a gksudo->kdesudo symlink. pkexec can also be used I believe, but it will requite command line parameters update, not just gksudo->pkexec binary substitution in script;
- I am using KDE, but service is currently working with lightdm or gdm, so I can't proceed without serious update here;
Here is the patch, that will fix compatibility with python2-psutil version 2.x: http://pastebin.com/JtmP5kDk

If somebody using gdm/lightdm, you should get working setup after applying all this, but I will wait for official KDE support (I am too lazy to add it myself since I don't really need unattended access to my laptop)

ava1ar commented on 2014-07-10 03:37

Thanks for the quick update. Actually, there is another problem exists: chrome-remote-desktop requires python2-psutil of version 1.x, while only 2.x exists in Arch repos.
With 2.x I am getting following exception while trying to launch it:

Traceback (most recent call last):
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1210, in <module>
sys.exit(main())
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 971, in main
pid = get_daemon_pid()
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 509, in get_daemon_pid
except psutil.error.Error:
AttributeError: 'ModuleWrapper' object has no attribute 'error'

I am currently trying to patch it for version 2.x. Will post an update shortly.

ava1ar commented on 2014-07-10 02:06

Symlinking whole directory /opt/chrome/native-messaging-hosts to /etc/chromium/native-messaging-hosts is not a good idea. If user has something installed to /etc/chromium/native-messaging-hosts (i.e. lastpass), package will fail to install due to attempt to overwrite existing dir. Much better is symlinking of required files. Only thing you need is replace last line

ln -sr opt/chrome/native-messaging-hosts chromium/native-messaging-hosts
with
ln -sr opt/chrome/native-messaging-hosts/* chromium/native-messaging-hosts

This will symlink every individual file and avoid conflicts with other chromium addons.

sacarde commented on 2014-07-09 18:27

OK

thanks a lot

Anonymous comment on 2014-07-09 16:25

Ops, "systemctl --user enable chrome-remote-desktop.service"

Anonymous comment on 2014-07-09 16:18

@sacarde It's a user service, you need to use systemd on user mode (--user) to start it.
Try "systemctl --user list-unit-files" and "systemctl enable chrome-remote-desktop.service" as your own user.