Package Details: chrome-remote-desktop 133.0.6943.7-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: 124
Popularity: 0.093473
First Submitted: 2014-04-27 23:43 (UTC)
Last Updated: 2025-02-04 19:33 (UTC)

Pinned Comments

frealgagu commented on 2020-12-05 22:38 (UTC)

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.chrome-remote-desktop/releases/

victorbrca commented on 2020-04-03 01:04 (UTC)

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 (UTC)

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 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 33 Next › Last »

<deleted-account> commented on 2016-12-07 12:20 (UTC)

@DaveB: Sorry man, still not working. I remove google-chrome & chrome-remote-desktop from my server. Also removed pacaur & pacman caches. Removed all config files of chrome-remote-desktop & all cache files of google-chrome. Afterwards, rebooted my Arch Server. First installed google-chrome, then chrome-remote-desktop, then the CRD app in google chrome. Log file: http://pastebin.com/Lrg9DGMX

DaveB commented on 2016-12-06 10:00 (UTC)

Hey Timo, I can't tell from here what has happened, but it seems likely that you still had the server running in an older instance. Could you try killing all instances of the server and then try running the server again? (Or maybe rebooting the machine if convenient)

<deleted-account> commented on 2016-12-06 09:47 (UTC)

@DaveB Sorry man, still not working for me. Using google-chrome from AUR as my browser. Full cleanup before installation (reinstalled google-chrome, deleted config files). Paste of log: http://pastebin.com/nswAnuvf

DaveB commented on 2016-12-04 22:02 (UTC)

PLEASE READ THIS BEFORE YOU UPDATE There have been significant changes in this release that I can't trace back. The server should work (tested here), but I can't guarantee compatibility with your browser (especially if it's Chromium) or with your DE. If you're using v5.2 and you're happy with it, please stick to it or keep a backup of the old version until you're sure the new one works. Google has removed the old version from the servers.

DaveB commented on 2016-11-19 08:22 (UTC)

@Mike, it's the out of date issue.

MikeW50 commented on 2016-11-18 20:51 (UTC)

I'm getting the error: curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_52.0.2743.74_amd64.deb Aborting... while running makepkg. Is this the out of date issue, or should I be looking for a different problem?

DaveB commented on 2016-11-18 19:35 (UTC) (edited on 2016-11-18 19:49 (UTC) by DaveB)

I'm going to leave it at this version and mark it out of date until Chromium is updated. I'm guessing that Chromium's outdated Native Client is one of the problems, and until that's updated, there isn't much I can do. ETA: pnacl isn't it, I tried c/p-ing the chrome version into it – didn't work.

<deleted-account> commented on 2016-11-18 10:32 (UTC)

@DaveB No problem man, take your time. It's not critical for me. Mainly use it for my homeserver, but will use VNC for the time being. Is Chrome also v52 when you tried it? Version differences between chrome & chrome remote desktop might explain downgrade issues.

DaveB commented on 2016-11-18 10:15 (UTC) (edited on 2016-11-18 10:21 (UTC) by DaveB)

@Timo That'S right, the package has been deleted upstream. I only downgraded it to prevent other users attempting to upgrade and getting an error. I've reinstalled 52 and it doesn't seem to be working anymore with chrome (I get into the machine but session won't start) or chromium (complains that NaCl isn't working, but I suspect there's another problem that I'll have to look into). I'm trying to get 55 to work again, same deal. The pnacl version in Chromium is older than in Chromium. That might explain things. Doesn't solve your problem though.

<deleted-account> commented on 2016-11-18 09:35 (UTC)

@DaveB Thanks for the quick response! Seems that something went wrong with downgrading since now I get a error 404 when trying to install through pacaur (pacakge v52 not available anymore?) Pastebin of error log http://pastebin.com/WxvuDD4X

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 33 Next › Last »