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.137836
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 .. 10 11 12 13 14 15 16 17 18 19 20 .. 33 Next › Last »

afg984 commented on 2018-04-26 07:58 (UTC) (edited on 2018-04-26 07:59 (UTC) by afg984)

The problem happens even if I run crd --start after a reboot. (note I did not systemctl enable --user chrome-remote-desktop.service)

I might be wrong, but I think this line in the log suggests that it actually successfully started the X server:

INFO:X server is active.

I'm suggesting that xorg-xrandr as a dependency because it seems to be using xrandr to test whether resizing is supported. Line 563 crashes with OSError: [Errno 2] No such file or directory if the executable does not exist.

/opt/google/chrome-remote-desktop/chrome-remote-desktop

 540   def _launch_xvfb(self, display, x_auth_file, extra_x_args):
 562     with open(os.devnull, "r+") as devnull:
 563       exit_code = subprocess.call("xrandr", env=self.child_env,
 564                                   stdout=devnull, stderr=devnull)
 565     if exit_code == 0:
 566       # RandR is supported
 567       self.server_supports_exact_resize = True
 568       self.server_supports_randr = True
 569       self.randr_add_sizes = True

frealgagu commented on 2018-04-24 14:02 (UTC)

@afg984 It looks like your :20 DISPLAY is being already used and it's impossible to start session, try to kill all chrome-remote-desktop process and try again (restart if is possible is even better).

afg984 commented on 2018-04-24 12:00 (UTC)

xorg-xrandr seems to be a dependency, see error log:

https://pastebin.com/R7iAiAX4

frealgagu commented on 2018-03-29 00:18 (UTC)

@sl1pkn07 I've not found a way to do that, chrome-remote-desktop uses the :20 DISPLAY, there are forums in ubuntu that shows a way to do it but it contains errors and crashes. @Kuchiriel there is a file you need to change ~/.chrome-remote-desktop where you choose to start a new session in one of your installed desktop environments. It should be only to uncomment a line and you're ready.

Kuchiriel commented on 2018-03-29 00:05 (UTC)

I am using the latest Manjaro and getting this.

Killing process 2034 [0328/210429.150449:INFO:remoting_user_session.cc(688)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20180328_210429_geGiYH' Using host_id: c6c24ea3-a799-afe2-e5e8-edc2189c6068 Launching X server and X session. Starting Xvfb on display :20 X server is active. Launching X session: ['/bin/sh', '/home/trevor/.chrome-remote-desktop-session'] Launching host process ['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/trevor/.config/chrome-remote-desktop/pulseaudio#bd9f957780/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.trevor.ssh_auth_sock', '--signal-parent'] wait() returned (2373,0) Session process terminated Failure count for 'session' is now 1 Terminating X server Terminating host Failure count for 'X server' is now 0 Failure count for 'host' is now 0 Waiting before relaunching wait() returned (2372,256) Waiting before relaunching

sl1pkn07 commented on 2018-03-26 17:28 (UTC)

all fixed

How can I access the same X session when an X session is already open, instead of open a new X session?

frealgagu commented on 2018-03-21 23:11 (UTC)

Please reinstall and let me know if you have troubles.

parpel commented on 2018-03-21 18:29 (UTC) (edited on 2018-03-21 18:30 (UTC) by parpel)

This is broken for me, I am getting:

/usr/bin/crd: /opt/google/chrome-remote-desktop/chrome-remote-desktop: 
/usr/bin/python22: bad interpreter: No such file or directory

Is there any workaround for this?