Package Details: chrome-remote-desktop 72.0.3626.12-1

Git Clone URL: (read-only)
Package Base: chrome-remote-desktop
Description: Access other computers or allow another user to access your computer securely over the Internet
Upstream URL:
Keywords: Chrome Chromium Google Networking Remote
Licenses: BSD
Submitter: None
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 98
Popularity: 1.618313
First Submitted: 2014-04-27 23:43
Last Updated: 2019-01-12 21:11

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Horus125 commented on 2019-03-23 20:56

If anyone wants to use the current xsession (display: 0) you can follow the answer here (from MDMower) I also had to add an extra pam rule to get it working, like @zhtlancer said

zhtlancer commented on 2019-03-08 02:17

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
account     required
password    required
session     required

mazieres commented on 2019-02-28 17:58

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.)

aztec102 commented on 2019-01-16 16:39

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

I need help.

Wernight commented on 2019-01-11 08:49

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.

bdefore commented on 2018-12-08 15:26

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.

frealgagu commented on 2018-11-17 20:56

@mradi have you found the way to use it in :0 display ?

bluerider commented on 2018-11-05 21:14

==> Validating source files with sha256sums... chrome-remote-desktop-71.0.3578.31.deb ... FAILED

Looks like the sha256sums are different.

specter119 commented on 2018-10-24 02:26

I think it need the xorg-xrandr as dependency

adrioanocr commented on 2018-09-10 22:16

Is there way to have CRD use the same xsession that's currently running instead of spinning up a new one?