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: 1.01
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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 32 Next › Last »

DaveB commented on 2017-10-16 11:33 (UTC)

@Pallegro thanks for the heads up

pallegro commented on 2017-10-15 15:27 (UTC)

fyi, this depends on gtk3 instead of gtk2 now

DaveB commented on 2017-09-19 13:45 (UTC)

Thanks :) There shouldn't be a resource difference since either method does much the same thing, but autostarting using systemd may run some single-instance programs in the CRD session that you'd want to use in your native desktop session.

annoyingduck commented on 2017-09-19 02:30 (UTC)

Bravo on this package, makes installing a breeze. 2 questions: is there a big resource difference between autostarting via systemctl --user enable chrome-remote-desktop.service or adding crd to the startup applications? 2nd: on Windows there is a clear notification that the desktop is being accessed/actions can be seen on the target computer screen, but not on Linux (there is zero indication that another computer is accessing the target machine). Anyone come up with a way to tell if your computer is being accessed via crd?

DaveB commented on 2017-06-02 21:00 (UTC)

Done. What a messy update. Thanks for alpha and beta testing, spider-mario and Zeroedout.

spider-mario commented on 2017-06-01 21:57 (UTC)

Also, I think the new line: echo "export $(dbus-launch)" >> ... should use single quotes, not double quotes.

Zeroedout commented on 2017-06-01 17:58 (UTC)

MD5sum failed on crd. "... crd ... FAILED ..."

kokeroulis commented on 2017-05-26 18:43 (UTC)

I am trying to install the crd and i am seeing the following error, https://gist.github.com/anonymous/8adc4167794ff363a549a0781aa28147 does anyone know how i can fix this? The package xorg-xrandr is installed and the version is 1.5.0-1

DaveB commented on 2017-05-23 07:58 (UTC)

PSA: Chrome Remote Desktop is not part of the Google Chrome package. The CRD versions lag behind.

Kuchiriel commented on 2017-05-09 04:48 (UTC)

Someone please create an openrc package of this!

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