Package Details: chrome-remote-desktop 85.0.4183.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: 113
Popularity: 0.85
First Submitted: 2014-04-27 23:43
Last Updated: 2020-07-28 05:00

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

Latest Comments

« First ‹ Previous ... 11 12 13 14 15 16 17 18 19 20 21 ... Next › Last »

DaveB commented on 2016-04-01 07:42

Unfortunately, there doesn't seem to be an i686 version anymore, getting a 404 error from the direct link and the download page. Will update as and when there is a 32-bit version available.

DaveB commented on 2016-03-02 21:46

@dlh I'm leaving it at nano, as setting up nano as a default editor is a pain and I don't want to subject anyone to vi as the default editor if they just want to install this package.

dlh commented on 2016-02-29 21:07

@DaveB: You should not require nano, but instead invoke editor that is specified in EDITOR env variable.

DaveB commented on 2016-02-25 22:05

ephemient: Done, thanks for your help!

ephemient commented on 2016-02-25 20:45

Could you change

@@ -16,3 +16,3 @@
-_arch=i386
-[ "$CARCH" == x86_64 ] && _arch=amd64
-source=("https://dl.google.com/linux/direct/${pkgname}_current_${_arch}.deb"
+source_i686=("http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_i386.deb")
+source_x86_64=("http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_amd64.deb")
+source=(
@@ -21 +21,3 @@
-md5sums=('SKIP'
+md5sums_i686=('bf9135f439fa4bfa1daf16e96c62d87a')
+md5sums_x86_64=('90cd272f1758617478380906f5cbc219')
+md5sums=(

please? Using _current.deb breaks for those of us caching with /etc/makepkg.conf:SRCDEST and there's no reason not to include checksums.

Det commented on 2015-12-16 12:48

"cd "$srcdir"" is redundant.

DaveB commented on 2015-12-08 22:07

Det, could you please stop flagging this out of date? I check it every day, it is up to date.

DaveB commented on 2015-11-30 14:43

You're welcome :)

Paviluf commented on 2015-11-30 12:21

Yes problem solved. At least there is some useful info on the comments about this now.

Sorry for the inconvenience Dave and thank you for your work ;)

DaveB commented on 2015-11-30 06:14

I'm not going to do that, as it would involve providing support for Google's product and open up a whole new channel of sorrow and pain and wasted Sunday afternoons. That's not specifically aimed at you Jeremy. I can't provide support for CRD itself as that would involve keeping track of CRD and that changes Google might make to it, which would involve constantly installing and uninstalling CRD and the permissions in the browser and everything or I run the serious risk of giving outdated info. I just don't have the time to do that, and I don't have to as CRD itself is not my product to provide support for. It's outside my jurisdiction. I have to assume that people using CRD are able to follow the instructions provided by Google, even if that assumption obviously won't withstand the reality test.

Other than that, can I assume that the problem is solved?