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

jamesan commented on 2014-08-16 11:42 (UTC)

Perhaps we can add an install file that reminds the user to create a ~/.chrome-remote-desktop-session file and ~/.config/chrome-remote-desktop folder after installation and before enabling remote connections with the browser extension in order to get this working.

jamesan commented on 2014-08-16 11:40 (UTC)

The two condition lines in the systemd service unit file should go under the Unit heading, not the Service heading. Systemd complains it doesn't understand these lines under the Service heading and ignores them. ----- Also managed to resolve that problem where the systemd service unit would launch the X session which would immediately terminate. The user starting the service needs to have a file, ~/.chrome-remote-desktop-session, that contains a single line with the command launching the X session. For me using (SLiM/)XFCE4, that's simply startxfce4. Other suggestions include: - /etc/X11/Xsession - /usr/bin/openbox-session - /usr/bin/lxsession -s Lubuntu -e LXDE ----- The steps I took to get the whole thing running: 1. Install this AUR package. 2. Create the folder, ~/.config/chrome-remote-desktop 3. Create the file, ~/.chrome-remote-desktop-session, with the single line, "startxfce4" 4. Install the Chrome Remote Desktop extension to either Chrome or Chromium. 5. Launch the extension and "Enable Remote Connections" (this creates the host#...json file in ~/.config/chrome-remote-desktop) 6. Start and enable the chrome-remote-desktop systemd service. 7. Confirm the service successfully starts an X session and connect to this computer with another computer/phone/etc.

jamesan commented on 2014-08-16 09:59 (UTC)

I get the same error as muhas both when starting the systemd service unit and when starting it manually (/opt/google/chrome-remote-desktop/chrome-remote-desktop --start) while using SLiM/XFCE4. Not sure how to get passed this... I might test this on GDM/GNOME 3 if I get the time.

<deleted-account> commented on 2014-08-15 17:21 (UTC)

Unfortunately I have yet to find any way to track whenever there is a new update. So, if you ever get a md5sum mismatch, you should do this: Open the deb and check if the control file inside control.tar.gz shows a different version. If so, just flag as out of date. If the version is correct, just comment here that the md5sums are wrong for some reason. I added two conditions to the service, now you should only be able to run it if ~/.config/chrome-remote-desktop is non-empty and there's a host#*.json file inside of it. If you have ever any problems unrelated to the packaging, just file a bug at http://crbug.com and link it here so other affected users can star it. Also, remember to link here from the bug report so the devs can confirm it really isn't a packaging error.

vendion commented on 2014-08-14 10:45 (UTC)

Did anyone need to create a "$HOME/.chrome-remote-desktop-session" file like the setup directions states (https://support.google.com/chrome/answer/1649523)? This still isn't working for me and not sure if it is caused by my Login Manager (SLiM) or my window manager (Wingo).

silverhammermba commented on 2014-08-14 02:22 (UTC)

I had no problems getting this to work. After installing the package 1. mkdir ~/.config/chrome-remote-desktop 2. Run app and enable remote connections 3. Enable user service

delin commented on 2014-08-07 18:54 (UTC)

Additional, need to: sudo mkdir /etc/chrome-remote-desktop-session systemctl --user enable chrome-remote-desktop.service systemctl --user start chrome-remote-desktop.service but, on connect: [30935.930103] ChromotingNetwo[4523]: segfault at e0 ip 00000000004e676d sp 00007f3f91c03320 error 4 in chrome-remote-desktop-host[400000+5e4000]

muhas commented on 2014-08-01 06:36 (UTC)

systemctl start chrome-remote-desktop.service Failed to start chrome-remote-desktop.service: Unit chrome-remote-desktop.service failed to load: No such file or directory. /opt/google/chrome-remote-desktop/chrome-remote-desktop --start 2014-08-01 10:34:13,158:INFO:Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20140801_103413_ACW0AG' Using host_id: eb4a9968-0a7c-1cdc-b0b5-2effb06d740d Launching X server and X session. Cleanup. Log file: cat /tmp/chrome_remote_desktop_20140801_103413_ACW0AG Exception IOError: (9, 'Bad file descriptor') in <bound method _TemporaryFileWrapper.__del__ of <closed file '<fdopen>', mode 'w+b' at 0x7ff9f2283780>> ignored 2014-08-01 10:34:13,159:INFO:Using host_id: eb4a9968-0a7c-1cdc-b0b5-2effb06d740d 2014-08-01 10:34:13,160:INFO:Launching X server and X session. Traceback (most recent call last): File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1243, in <module> sys.exit(main()) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1170, in main desktop.launch_session(args) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 471, in launch_session self._launch_x_server(x_args) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 369, in _launch_x_server if (len(x_session) == 2 and TypeError: object of type 'NoneType' has no len() 2014-08-01 10:34:13,178:INFO:Cleanup

vendion commented on 2014-07-22 02:27 (UTC)

@CharlesAtum even without the service running when I Enable Remote Connections from the chrome app I get: "Failed to start remote access service" See http://imgur.com/frFFKrf I may not have my .chrome-remote-desktop-session file right, that or it doesn't like something about my setup (SLiM for login manager and Wingo for WM).

<deleted-account> commented on 2014-07-21 14:14 (UTC)

@vendion You should run the Chrome Remote Desktop app first and Enable Remote Connections there. After that the service can be run. Also, I may add the "ConditionDirectoryNotEmpty" condition on a future pkgrel.

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