Package Details: chrome-remote-desktop 84.0.4147.39-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: 112
Popularity: 1.30
First Submitted: 2014-04-27 23:43
Last Updated: 2020-06-26 18:04

Pinned Comments

victorbrca commented on 2020-04-03 01:04

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

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

WhiteHatHacker1 commented on 2015-03-13 18:06

I order to get my install working, I did what @mobabur94 typed (+1 for great instructions), but I had to do something a little different for the symlink. Because I already had another program that created the native-messaging-hosts directory, I couldn't link "/etc/opt/chrome/native-messaging-hosts/" to "/etc/chromium". Instead, I did this: "ln -s /etc/opt/chrome/native-messaging-hosts/* /etc/chromium/native-messaging-hosts/", in addition to deleting the link already there named "*".

WhiteHatHacker1 commented on 2015-03-12 22:13

I manually created the chrome-remote-desktop group, added myself to it, created the ~/.chrome-remote-desktop-session file with "exec cinnamon-session-cinnamon" in it, and created the ~/.config/chrome-remote-desktop directory, but did not change the symlink, because I already had to for LastPass, and I get a "Could not connect to the network" message from the App.

Does anybody have a solution?

mobabur94 commented on 2015-03-12 20:04

In order to get it working:

1. I manually created the chrome-remote-desktop group, and added myself to it.
2. I manually created the ~/.chrome-remote-desktop-session file with "exec startxfce4" in it.
3. I manually created the ~/.config/chrome-remote-desktop directory.
4. I manually changed the symlink for chromium using: "ln -s /etc/opt/chrome/native-messaging-hosts/ /etc/chromium" (@ishitatsuyuki is right)

Also, I never used systemctl to start or enable the chrome-remote-desktop service; if I am not mistaken, the extension is supposed to invoke the python script.

After all that, I was able to get it to show the "Enable remote connections" button. Clicking that button generates the host json file in ~/.config/chrome-remote-desktop.

Now, connecting from another computer successfully starts xfce. But it starts it on :20, not :0, which I guess is expected, since the python script tries to get "a candidate display number for which there is currently no x server lock file".

Although, it logs in using my user, chromium within the remote connection uses a blank profile, which gets created in ~/.config/chrome-remote-desktop/chrome-profile. I haven't tried to symlink that to ~/.config/chromium because the python script suggests to sign in and sync.

I am not sure why remote assistance is allowed to use :0 while remote desktop needs to use :20...

Perhaps package maintainer can fix the symlink and the groupadd.

mobabur94 commented on 2015-03-12 20:01

In order to get it working:

1. I manually created the chrome-remote-desktop group, and added myself to it.
2. I manually created the ~/.chrome-remote-desktop-session file with "exec startxfce4" in it.
3. I manually created the ~/.config/chrome-remote-desktop directory.
4. I manually changed the symlink for chromium using: "ln -s /etc/chromium/native-messaging-hosts /etc/opt/chrome/native-messaging-hosts" (@ishitatsuyuki is right)

Also, I never used systemctl to start or enable the chrome-remote-desktop service; if I am not mistaken, the extension is supposed to invoke the python script.

After all that, I was able to get it to show the "Enable remote connections" button. Clicking that button generates the host json file in ~/.config/chrome-remote-desktop.

Now, connecting from another computer successfully starts xfce. But it starts it on :20, not :0, which I guess is expected, since the python script tries to get "a candidate display number for which there is currently no x server lock file".

Although, it logs in using my user, chromium within the remote connection uses a blank profile, which gets created in ~/.config/chrome-remote-desktop/chrome-profile. I haven't tried to symlink that to ~/.config/chromium because the python script suggests to sign in and sync.

I am not sure why remote assistance is allowed to use :0 while remote desktop needs to use :20...

Perhaps package maintainer can fix the symlink and the groupadd.

ishitatsuyuki commented on 2015-02-22 02:48

Linking * seems to do wrong thing.
It make a link named \*.

7i7o commented on 2015-01-15 05:11

You should list xorg-xrandr as a dependency.

Line 425 of the google-remote-desktop service script calls xrandr and throws an exception when not installed (had a REALLY light desktop with no need for extra xorg-server-utils and couldn't start service because of that).

Installed it and voila! Remote desktop up and running (took me a couple of hours to discover it since i'm not a debug-friendly kind of guy.

camio commented on 2015-01-08 00:15

When installing I received the following error "groupadd: invalid group ID 'chrome-remote-desktop'". I'm not sure how critical this is.

agnotek commented on 2014-12-23 16:49

use this PKGBUILD:

# Maintainer: Mateus Rodrigues Costa <charles [dot] costar [at] gmail [dot] com>

pkgname=chrome-remote-desktop
pkgver=40.0.2214.44
pkgrel=2
pkgdesc="Allows you to securely access your computer over the Internet through Chrome."
url="https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp"
arch=('i686' 'x86_64')
license=('BSD')
install=$pkgname.install
depends=('python2' 'python2-psutil' 'gconf' 'gtk2' 'nss'
'xorg-xdpyinfo' 'xorg-setxkbmap' 'xorg-server-xvfb' 'xorg-xauth')
source=("chrome-remote-desktop.service")
md5sums=('cde1758e875ff114cc8153edb7087d2a')
_arch=i386
if [ "$CARCH" == i686 ]; then
md5sums+=('8cf84e5801c3b5c6cff0a9efb2b1ba6a')
elif [ "$CARCH" == x86_64 ]; then
_arch=amd64
md5sums+=('03aaba1f91dbd1da367dc3ff4e0c5c3a')
fi
source+=(${pkgname}_${pkgver}_$_arch.deb::https://dl.google.com/linux/direct/${pkgname}_current_$_arch.deb)

package() {
msg2 "Extracting data.tar.gz"
bsdtar -xf data.tar.gz -C "$pkgdir/"

msg2 "Patching Python script"
sed -e '1 s/python/python2/' \
-e '/^.*sudo_command =/ s/"gksudo .*"/"pkexec"/' \
-e '/^.*command =/ s/s -- sh -c/s sh -c/' \
-i "$pkgdir"/opt/google/chrome-remote-desktop/chrome-remote-desktop

msg2 "Removing things that won't work"
rm -R "$pkgdir"/etc/cron.daily/
rm -R "$pkgdir"/etc/init.d/
rm -R "$pkgdir"/etc/pam.d/

msg2 "They forgot the LICENSE file, using the copyright file instead"
install -Dm644 "$pkgdir"/usr/share/doc/$pkgname/copyright "$pkgdir"/usr/share/licenses/$pkgname/copyright

msg2 "Adding a systemd user service"
install -Dm644 "$srcdir"/$pkgname.service "$pkgdir"/usr/lib/systemd/user/$pkgname.service

msg2 "Creating symlinks for chromium compatibility"
mkdir -p "$pkgdir"/etc/chromium/native-messaging-hosts
ln -sr "$pkgdir"/etc/opt/chrome/native-messaging-hosts/* "$pkgdir"/etc/chromium/native-messaging-hosts
}

txomon commented on 2014-12-17 10:00

md5sum for amd64 deb is c3882feb4f11eea34d7d05bc44d268c9

Stephen12 commented on 2014-11-11 10:47

How does it work?? https://www.apponfly.com/en/ @Brandon? Others?
@CharlesAtum did jamesan finally adopt it??? I might be interested..