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: 122
Popularity: 0.007993
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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 32 Next › Last »

bluerider commented on 2018-11-05 21:14 (UTC)

==> Validating source files with sha256sums... chrome-remote-desktop-71.0.3578.31.deb ... FAILED

Looks like the sha256sums are different.

specter119 commented on 2018-10-24 02:26 (UTC)

I think it need the xorg-xrandr as dependency

adrioanocr commented on 2018-09-10 22:16 (UTC)

Is there way to have CRD use the same xsession that's currently running instead of spinning up a new one?

mradi commented on 2018-09-09 03:58 (UTC) (edited on 2018-09-09 12:54 (UTC) by mradi)

I updated my graphics card to nvidia, and updated GDM, gnome. I followed the post to use display :0 as my chrome-remote-desktop and it worked fine. but when I recently tried it, again I started seeing errors like this, can someone help

2018-09-08 23:47:04,227:INFO:Using host_id: 529e63f8-0684-5932-d0a4-5bfa5866cf66
2018-09-08 23:47:04,228:INFO:Launching X server and X session.
2018-09-08 23:47:04,244:INFO:X server is active.
2018-09-08 23:47:04,623:INFO:Launching X session: ['/bin/sh', '/home/xyz/.chrome-remote-desktop-session']
2018-09-08 23:47:04,625:INFO:Launching host process
2018-09-08 23:47:04,625:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/xyz/.config/chrome-remote-desktop/pulseaudio#20383fe03b/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.xyz.ssh_auth_sock', '--signal-parent']
2018-09-08 23:47:04,627:INFO:wait() returned (6740,0)
2018-09-08 23:47:04,627:INFO:Session process terminated
2018-09-08 23:47:04,640:INFO:Failure count for 'session' is now 1
2018-09-08 23:47:04,640:INFO:Terminating host
2018-09-08 23:47:04,641:INFO:Failure count for 'X server' is now 0
2018-09-08 23:47:04,641:INFO:Failure count for 'host' is now 0
2018-09-08 23:47:04,641:INFO:Waiting before relaunching
2018-09-08 23:47:06,643:INFO:wait() returned (6739,0)
2018-09-08 23:47:06,644:INFO:Waiting before relaunching
2018-09-08 23:47:09,630:INFO:Launching X server and X session.
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 1685
2018-09-08 23:47:09,648:INFO:X server is active.
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 534
2018-09-08 23:47:09,798:INFO:Launching X session: ['/bin/sh', '/home/xyz/.chrome-remote-desktop-session']
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 705
2018-09-08 23:47:09,800:INFO:Launching host process
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit
    self.flush()
  File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
Logged from file chrome-remote-desktop, line 1692
2018-09-08 23:47:09,800:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/xyz/.config/chrome-remote-desktop/pulseaudio#20383fe03b/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.xyz.ssh_auth_sock', '--signal-parent']

Nowaker commented on 2018-07-22 20:48 (UTC)

systemctl --user start chrome-remote-desktop gets me this:

Jul 22 15:33:18 nwkr-desktop crd[762]: OAuth credentials are invalid - exiting.

Still, clicking "Enable remote connections" in CRD App works totally fine.

What went wrong?

AlexWayfer commented on 2018-07-02 10:59 (UTC)

Please, use version for package filename:

https://github.com/Jguer/yay/issues/523#issuecomment-401761706

zjhzxhz commented on 2018-06-04 12:38 (UTC) (edited on 2018-06-04 13:16 (UTC) by zjhzxhz)

This package is not working in GNOME 3.28. I followed the instruction of this post but it is still not working.

Here's the config of .chrome-remote-desktop-session:

export $(dbus-launch)
# exec classic gnome-session --session gnome-classic
exec gnome-session
# exec gnome-session

Here's the output of crd --start:

Seems like you haven't activated CRD in your browser. Please do that before trying to run the server.

Here's the output of crd --restart:

The daemon is not currently running
[0604/203645.811960:INFO:remoting_user_session.cc(688)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20180604_203645_zOair2'
Cleanup.
Log file: /tmp/chrome_remote_desktop_20180604_203645_zOair2

The log file /tmp/chrome_remote_desktop_20180604_203645_zOair2 says that:

Failed to load config: [Errno 2] No such file or directory: '/home/hzxie/.config/chrome-remote-desktop/host#<hash-code>.json'
2018-06-04 20:36:45,947:INFO:Cleanup.
[0604/203645.952871:WARNING:remoting_user_session.cc(464)] Child exited with status 1

Here's the output of systemctl status --user chrome-remote-desktop:

● chrome-remote-desktop.service - "Chrome Remote Desktop host daemon"
   Loaded: loaded (/usr/lib/systemd/user/chrome-remote-desktop.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Mon 2018-06-04 20:25:07 CST; 8min ago
           └─ ConditionPathExistsGlob=/home/hzxie/.config/chrome-remote-desktop/host#*.json was not met

I also tried to Enable Remote Connection from the Chrome application, but I got the following message after setting 6-digit PIN:

Enabling remote connections for this computer...

After about 20 min it finally timed out and I got this:

Failed to start remote access service.

Who can help me out? Thank you so much!

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