Package Details: chrome-remote-desktop 130.0.6723.14-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: 123
Popularity: 0.59
First Submitted: 2014-04-27 23:43 (UTC)
Last Updated: 2024-10-16 18:54 (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 .. 11 12 13 14 15 16 17 18 19 20 21 .. 32 Next › Last »

klepz commented on 2018-03-04 22:25 (UTC)

Morganamilo, fixed.

Morganamilo commented on 2018-03-04 22:01 (UTC)

chrome-remote-desktop_current_amd64.deb checksums fail for me.

BlackLotus89 commented on 2018-02-10 22:01 (UTC) (edited on 2018-02-10 22:01 (UTC) by BlackLotus89)

sed -e '1 s/python/python2/'

became unnecessary and actually breaks the script

AuR commented on 2018-01-27 17:28 (UTC)

Thanks for the starain's patch.

pogtastic commented on 2018-01-16 15:08 (UTC)

Confirming that starain's patch works perfectly. Thank you very much.

<deleted-account> commented on 2018-01-02 17:44 (UTC)

Hello, I also have the same problem:

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Hubo fallos durante la descarga de http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_61.0.3163.20_amd64.deb Cancelando...

Cheers. :D

fulgor commented on 2017-12-22 21:00 (UTC)

I have this error the link to the deb package is not found

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_61.0.3163.20_amd64.deb

arafey commented on 2017-12-16 20:52 (UTC)

@1ace: I just transferred the package to you.

1ace commented on 2017-12-15 11:43 (UTC)

@DaveB: I'm willing to adopt this package if you don't want to maintain it anymore :)

On top of the other comments people already posted, the current makedepends=('nano') is incorrect as well: the current script uses nano as runtime, not during the build, so it would be a normal depends, but it shouldn't enforce nano anyway, but instead use $EDITOR, thus dropping nano from any kind of depends.

m3thodic commented on 2017-12-10 01:08 (UTC)

@starain I forked your gist, added some deps and also enforced suid bit to user only. For anyone having issues, try using this gist in place of /opt/google/chrome-remote-desktop/chrome-remote-desktop: https://gist.github.com/tonylambiris/d9b37f224b166a823eb8115911114019

You will just have to change DEFAULT_SIZES to your regular resolution you run X at. You may also have to change FIRST_X_DISPLAY_NUMBER to share your desktop like you normally would want to in a remote pc session. I found this by running sudo xdpyinfo | head -3 (running with sudo is intentional).

Lastly, I matched .config/chrome-remote-desktop/Size to reflect the resolution set in DEFAULT_SIZES. This file literally is 1 line with 3840x2160 in it. I believe that's everything to get you up and running.

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