Package Details: chrome-remote-desktop 85.0.4183.39-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: 113
Popularity: 0.85
First Submitted: 2014-04-27 23:43
Last Updated: 2020-07-28 05:00

Pinned Comments

victorbrca commented on 2020-04-03 01:04

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

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 2 3 4 5 6 7 8 9 10 ... Next › Last »

wreckabum commented on 2019-11-19 06:36

Hi, I'm new to Arch. I just try installing this package today, but .deb file failed Validating check with sha256sums. really appreciated for any help. thanks.

jdarnold commented on 2019-11-14 18:04

Failed validity check today.

baatochan commented on 2019-09-10 08:42

I have a problem with setting up this package.

After installation and running crd --setup the webapp shows me to "set up remote access". However when I try to do it I get No response received to getCredentialsFromAuthCode message after 30000 milliseconds. (tried that multiple times while doing other steps described below).

I did change the exec command (I'm using KDE Plasma on Manjaro) to exec /usr/share/sddm/scripts/Xsession "/usr/bin/startkde" and Size file to my resolution (1920x1080).

I'm not sure if I should set the webapp first or start the service. While starting the service I get:

● chrome-remote-desktop.service - "Chrome Remote Desktop host daemon"
Loaded: loaded (/usr/lib/systemd/user/chrome-remote-desktop.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Sep 10 10:31:23 BARTOSZ-PC3 systemd[976]: Started "Chrome Remote Desktop host daemon".
Sep 10 10:38:19 BARTOSZ-PC3 systemd[976]: Starting "Chrome Remote Desktop host daemon"...
Sep 10 10:38:19 BARTOSZ-PC3 crd[61840]: [0910/103819.694222:INFO:remoting_user_session.cc(691)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190910_1>
Sep 10 10:38:19 BARTOSZ-PC3 user-session[61851]: pam_unix(chrome-remote-desktop:session): session opened for user baatochan by (uid=1000)
Sep 10 10:38:19 BARTOSZ-PC3 crd[61840]: [0910/103819.698337:WARNING:remoting_user_session.cc(613)] Failed to read from message pipe. Please check log to determine host status.
Sep 10 10:38:19 BARTOSZ-PC3 crd[61840]: Log file: /tmp/chrome_remote_desktop_20190910_103819_okEMcp
Sep 10 10:38:19 BARTOSZ-PC3 user-session[61851]: pam_unix(chrome-remote-desktop:session): session closed for user baatochan
Sep 10 10:38:19 BARTOSZ-PC3 crd[61853]: The daemon is not currently running
Sep 10 10:38:19 BARTOSZ-PC3 systemd[976]: chrome-remote-desktop.service: Succeeded.
Sep 10 10:38:19 BARTOSZ-PC3 systemd[976]: Started "Chrome Remote Desktop host daemon".

And the log contains one line:

[0910/103819.698360:WARNING:remoting_user_session.cc(467)] Child terminated by signal 5

When running it with crd --start I get:

[0910/104319.642341:INFO:remoting_user_session.cc(691)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190910_104319_Im0hKu'
[0910/104319.646161:WARNING:remoting_user_session.cc(613)] Failed to read from message pipe. Please check log to determine host status.
Log file: /tmp/chrome_remote_desktop_20190910_104319_Im0hKu

and the log contains the same message.

Reading the comments here I checked the pam.d dir and there is the correct file created by the "installer".

Tbh don't know what to do now to move on with the set-up and I would be really grateful if someone could help me.

frealgagu commented on 2019-08-27 12:07

@nightuser yeah, that's the first hint. You can download the deb, extract it, extract the control packsge and see the control file to know the current version.

I'll update ASAP.

nightuser commented on 2019-08-27 08:11

The sha256 sum of the .deb isn't correct. Perhaps the package was updated on Google's servers?

apepa commented on 2019-08-15 19:04

Yes, I was unaware you needed to run crd in terminal to set it up. On first impression to a Linux novice like me it just looks like a simple process of building the package in pacman and running the app as it is with Chrome itself.

snipes040 commented on 2019-08-15 18:45

@frealgagu Ah ok that makes much more sense. Thanks for replying and updating this amazing package I appreciate it!

frealgagu commented on 2019-08-15 18:37

@snipes040 No, this is caused because a new version 76.0.3809.117 is available (and the artifact in download page is replaced). I'll update ASAP.

snipes040 commented on 2019-08-15 14:48

So how are we suppose to install this package? It worked on my (now broken install) but on a fresh install it fails the validity check. Is there something I'm missing now to get it installed/working with the new web version?

frealgagu commented on 2019-08-13 03:38

@apepa I've done it recently and it works, maybe there is some step you are missing? You need to execute some post installation commands, like configure the DE and chrome remote itself.