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

Latest Comments

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

oofnik commented on 2020-07-03 12:56

I think python-psutil should be listed as a dependency now that the CRD script has been refactored to use Python 3.

gphilippi commented on 2020-06-25 16:36

@ayushdutta321 weird. I created an access code right now on the "remote support" tab that I said before. I don't understand why it's not working there.

I honestly don't know what may be causing the problem. Sorry. Have you tried to reinstall the package?

ayushdutta321 commented on 2020-06-25 06:33

@gphillippi Yeah i have the chrome remote desktop extension installed. I can connect to my friends pc using his generated code but I am unable to generate my own code. Its prompting me to download a .deb file. No terminal is not necessary

gphilippi commented on 2020-06-19 15:28

@ayushdutta321 to do this, I usually use the link "https://remotedesktop.google.com/access" and access the "remote support" tab. Remember to install the remote chrome desktop extension in the chrome browser.

You need a command line to do it?

ayushdutta321 commented on 2020-06-18 20:29

I have successfully started crd using crd --start after following steps by @victorbrca and I am also able to connect to the pc but only when both of the pc has the same gmail account signed it.

How to generate the crd remote support code and access the pc from any pc ?

gphilippi commented on 2020-05-28 16:00

Please, someone pins the comment of @victorbrca.

This resume all the process for using rcd.

Thanks @frealgagu, @Brinsky, @nightuser and @victorbrca.

wreckabum commented on 2020-05-20 01:57

After following @brinsky 's comment, It seems like audio comes out from my host machine only. Anyone having the same issue?

thibaultmol commented on 2020-05-18 22:04

@frealgagu @brinsky 's comment should be pinned https://aur.archlinux.org/packages/chrome-remote-desktop/?O=20&PP=10#comment-719586 it's essential for getting CRD to work

snipes040 commented on 2020-04-27 14:40

@nightuser that's awesome thanks for that!

However I can't seem to get that working it doesn't seem to be picking up that Xsession file in /chrome-remote-desktop/. Do I just copy and paste into the Xsession file that I created and remove the + and - signs? I tried it with the + and - signs as well.

Sorry for the noob questions.

nightuser commented on 2020-04-25 08:37

@snipes040 Display 20 is the correct behavior. CRD on Linux starts a new Xorg session instead of the existing one. If you still want to use display 0, see my patch below. It's a bit dirty and doesn't support sound forwarding yet, but, if anyone's interested, I may rewrite it slightly and add the missing features.