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 .. 15 16 17 18 19 20 21 22 23 24 25 .. 32 Next › Last »

Bittersourness commented on 2017-02-01 09:50 (UTC) (edited on 2017-02-01 09:55 (UTC) by Bittersourness)

@DaveB Hi! First of all, thanks for your big effort mantaining this package! However,I get the following message updating to the new version (56.0.2924.51-1): ==> Extracting sources… -> Extracting chrome-remote-desktop_56.0.2924.51_amd64.deb with bsdtar ==> Starting prepare()… -> Extracting data from debian package bsdtar: Error opening archive: Failed to open 'data.tar.gz' Replacing "data.tar.gz" with "data.tar.xz" in PKGBUILD solves the problem :)

smekkleysa commented on 2017-01-13 14:29 (UTC)

Partially solved the problem. I needed to install xorg-xrandr. I managed to make it work with xfce4 but not with gnome. So there is something wrong with the current version of gnome.

smekkleysa commented on 2017-01-13 11:00 (UTC) (edited on 2017-01-13 12:23 (UTC) by smekkleysa)

I get a following error, when I issue crd command. Does anyone have any idea? I've tried starting gnome in both wayland and xorg, but no success. I also tried with xfce4. It works on another machine, so there must be some dependencies missing 2017-01-13 19:58:14,333:INFO:Using host_id: cdf98a6c-249d-aa23-1eb6-69b23ae27810 2017-01-13 19:58:14,334:INFO:Launching X server and X session. 2017-01-13 19:58:14,349:INFO:Starting Xvfb on display :20 xdpyinfo: unable to open display ":20". 2017-01-13 19:58:14,865:INFO:X server is active. Traceback (most recent call last): File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1545, in <module> sys.exit(main()) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1472, in main desktop.launch_session(args) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 656, in launch_session self._launch_x_server(x_args) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 579, in _launch_x_server self._launch_xvfb(display, x_auth_file, extra_x_args) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 503, in _launch_xvfb stdout=devnull, stderr=devnull) File "/usr/lib/python2.7/subprocess.py", line 168, in call return Popen(*popenargs, **kwargs).wait() File "/usr/lib/python2.7/subprocess.py", line 390, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1024, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory 2017-01-13 19:58:14,878:INFO:Cleanup. 2017-01-13 19:58:14,879:INFO:Terminating X server

DaveB commented on 2016-12-15 08:10 (UTC)

@piedro, thanks for the info! Weird that I got it working on this machine though...

piedro commented on 2016-12-15 04:22 (UTC)

Hello Timo! I am having the same problems - to make sure I tried in a Ubuntu installation running on virtualbox. I used crd from there and on arch successfully in the past - now neither the arch nor ubuntu install works - I tried many times reinstallion, purging, deleting user profiles - nothing works... Is there any tutorial out there? I do not find any help or documentation - searching the web brings only up my own posts... So the good news for Dave is - it's not working under many circumstances - it's not the arch build! p.

<deleted-account> commented on 2016-12-14 21:27 (UTC)

@DaveB: Yeah, tried it again today after multiple reinstalls (and purging of config files), but no dice. I keep getting the Xvfb error that display :20 cannot be opened... So probably does not have something to do with CRD per se, but more about Xvfb. Will stay on VNC + Guacamole for now.

DaveB commented on 2016-12-07 13:19 (UTC)

@Timo Sorry, I've tried it here and it works, so I can't tell what's happening on your machine or what's going wrong. Getting crd going can be a nightmare especially getting the sequence right, and errors like the ones you describe do crop up. I'd love to be able to repeat the sequence but I can't remember exactly how I did it. Uninstalling/reinstalling Chrome probably won't help, as the old configs could still be in there lurking around. I'd suggest trying this, possibly again: 1. killing crd, then 2. completely erasing all the permissions in your Chrome, closing chrome (also instances in the background), reopening it again, setting up the permissions again and then trying to start crd. I think that was the sequence I used but since it took several attempts, I can't be certain.

<deleted-account> commented on 2016-12-07 12:20 (UTC)

@DaveB: Sorry man, still not working. I remove google-chrome & chrome-remote-desktop from my server. Also removed pacaur & pacman caches. Removed all config files of chrome-remote-desktop & all cache files of google-chrome. Afterwards, rebooted my Arch Server. First installed google-chrome, then chrome-remote-desktop, then the CRD app in google chrome. Log file: http://pastebin.com/Lrg9DGMX

DaveB commented on 2016-12-06 10:00 (UTC)

Hey Timo, I can't tell from here what has happened, but it seems likely that you still had the server running in an older instance. Could you try killing all instances of the server and then try running the server again? (Or maybe rebooting the machine if convenient)

<deleted-account> commented on 2016-12-06 09:47 (UTC)

@DaveB Sorry man, still not working for me. Using google-chrome from AUR as my browser. Full cleanup before installation (reinstalled google-chrome, deleted config files). Paste of log: http://pastebin.com/nswAnuvf

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