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.99
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 .. 24 25 26 27 28 29 30 31 32 Next › Last »

<deleted-account> commented on 2014-09-18 17:19 (UTC)

@jamesan Could you take a look if CRD still works if you remove the first sed line and change the dependencies from python 2 to 3?

gyurman commented on 2014-09-15 20:53 (UTC)

How can I connect to exciting session?

jamesan commented on 2014-09-13 18:33 (UTC)

Adopted this package. Let's see..: @vendion: I left out a couple steps apparently. Before step 5, the chrome-remote-desktop user group needs to be created and the hosting user must join that group: # groupadd chrome-remote-desktop # usermod -aG chrome-remote-desktop <username> Then, step 5 should generate the expected JSON file and not throw an error after your pin entry. Then, the chrome-remote-desktop user service can be started/enabled to receive remote connection requests. I'll try to codify some of this stuff in the PKGBUILD so there aren't as many or any manual steps needed to make this work after installing the package. Stay tuned...

<deleted-account> commented on 2014-08-29 16:50 (UTC)

Disowned, feel free to adopt it if you are interested.

vendion commented on 2014-08-29 02:04 (UTC)

@jamesan: Following you're seven step procedure I get to 5 before I run into any problems. I have created ~/.config/chrome-remote-desktop and I have "/home/vendion/gocode/bin/wingo" (this is used by Slim to start my window manager) in my ~/.chrome-remote-desktop-session file. When I click "Enable Remote Connections" and give it a pin, I get an error and the json file is never created in ~/.config/chrome-remote-desktop. Any ideas?

<deleted-account> commented on 2014-08-28 17:19 (UTC)

I lost interest in chrome-remote-desktop and will disown it soon. Anybody interested in adopting it? Maybe jamesan?

<deleted-account> commented on 2014-08-17 23:40 (UTC)

@jamesan I am not sure if a pkgver() function would be useful for a non development package: It would work for anyone installing the package for the first time, but I think I would still need to submit new versions so AUR helpers could detect a update. Also, The google-chrome packages maintained by Det show a way to know the new version by checking the repository metadata. There probably should be a way to do the same for CRD.

jamesan commented on 2014-08-16 12:27 (UTC)

More progress! Using the pkgver function, you can extract the debian package version from it's control file with the one-liner: pkgver() { bsdtar -xf control.tar.gz -O control | grep '^Version: ' | cut -f2 -d' ' } Observing the various Chrome/Chromium AUR packages, packages that do determine the version simply skip the checksum verification (i.e. chromium-browser-bin) allowing the PKGBUILD to perpetually track the latest release without intervention. Modified the PKGBUILD slightly to do this here: http://pastebin.com/z6tCi28F (PKGBUILD) http://pastebin.com/2qJVBVpL (PKGBUILD diff)

<deleted-account> commented on 2014-08-16 11:57 (UTC)

@jamesan Thanks for pointing out the service error, I knew it should be under the Unit heading but I didn't pay too much attention when I was actually changing the file. The install file currently only tells the user to create ~/.config/chrome-remote-desktop, I will add something about the desktop session file.

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 Next › Last »