Package Details: chrome-remote-desktop 101.0.4951.26-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: 118
Popularity: 0.75
First Submitted: 2014-04-27 23:43 (UTC)
Last Updated: 2022-04-18 01:18 (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

gameslayer commented on 2022-04-20 07:02 (UTC)

Chrome remote desktop still thinks I haven't installed it even tho I have and has the extension installed on the Chrome.

I couldn't find the service chrome-remote-desktop.service`` and when I ran/usr/bin/crd --startI get this messageSeems like you haven't set this up yet. Try running: crd --setup.``

And this is my log

[sudo] password for corey: 
Adding user corey to group chrome-remote-desktop
Checking that working directory and session file are present
That would be /home/corey/.config/chrome-remote-desktop and
/home/corey/.chrome-remote-desktop-session

Now entering the editor to make the appropriate changes to your session file.
Press any key to continue...

If you want to set a default size for all clients, please add a
value with format [width]x[height] (e.g 1360x768) in file
/home/corey/.config/chrome-remote-desktop/Size.
Remember that this will affect all clients you use.
If you dont want a default size please leave it blank.
Now entering the editor to make the appropriate changes to
your Size file. Do not enter any comments to this file.
Press any key to continue...

This completes the setup.

Please remember that you will need to allow Chrome or Chromium
to act as a server for this to work at all.

To do that, open https://remotedesktop.google.com/ in your chrome or chromium browser
and follow the instructions. Clicking the computer will open
it in the browser window in default resolution.
For a more pleasant chromoting experience, just issue the command: crd --restart

Happy chromoting! :)

Still doesn't work

ewuplse01 commented on 2022-04-18 04:00 (UTC)

The latest update of chrome-remote-desktop (101.0.4951.26-1) depends on libutempter. After upgrading, I needed to install libutempter in order for it to work.

frealgagu commented on 2021-11-08 15:17 (UTC)

Upgraded to version 96.0.4664.9, please flag package as out-of-date if checksum verification fails or 404 error is thrown downloading sources.

nightuser commented on 2021-11-08 12:39 (UTC) (edited on 2021-11-08 12:41 (UTC) by nightuser)

@Steven_He: Changing the link to the latest deb package and skipping the checksum check is wrong, since the package version will no longer represent the actual version of CRD. One can always obtain the latest version number and SHA256 hash from the Packages file in the CRD repository. I wrote a simple script that fetches this information from upstream and then updates the PKGBUILD file:

#!/bin/bash

. PKGBUILD
oldversion="$pkgver"
oldchecksum="${sha256sums[0]}"

data=($(curl -qs https://dl.google.com/linux/chrome-remote-desktop/deb/dists/stable/main/binary-amd64/Packages | grep '^Version\|^SHA256' | awk '{print $2}'))
version="${data[0]}"
checksum="${data[1]}"

echo "Updating $oldversion to $version"
sed -e "s,$oldversion,$version," -e "s,$oldchecksum,$checksum," -i PKGBUILD

Steven_He commented on 2021-11-08 09:23 (UTC)

Latest fix: Open PKGBUILD Change the URL under source into https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb Change the first long number under sha256sums into SKIP And then you can run makepkg -si like normal

gameslayer commented on 2021-11-07 07:57 (UTC)

Link for deb file is broken again, gives a 404 error when you install it

frealgagu commented on 2021-09-27 23:19 (UTC)

Upgraded to version 94.0.4606.27, please flag package as out-of-date if checksum verification fails or 404 error is thrown downloading sources.

gameslayer commented on 2021-09-27 06:57 (UTC) (edited on 2021-09-27 07:00 (UTC) by gameslayer)

Getting 404 issues when updating/installing the package again

Preparing...
Checking chrome-remote-desktop dependencies...
Resolving dependencies...
Checking inter-conflicts...
Download of xorg-server-xvfb (1.20.13-3) started
Download of xorg-server-xvfb (1.20.13-3) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Installing xorg-server-xvfb (1.20.13-3)...
A restart is required for the changes to take effect.
Cloning chrome-remote-desktop build files...
Generating chrome-remote-desktop information...

Building chrome-remote-desktop...
==> Making package: chrome-remote-desktop 93.0.4577.16-1 (Mon 27 Sep 2021 16:56:31)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading chrome-remote-desktop-93.0.4577.16.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_93.0.4577.16_amd64.deb
    Aborting...
Failed to build chrome-remote-desktop

The current link is

https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb

alphe commented on 2021-08-17 14:05 (UTC)

After upgrading to the latest version I am having issues to run gnome.

I am connencting correctly but I receive an error saying "Oh no something goes wrong please logout".

I tried to downgrade but I have the same issue.

The isssue is only with gnome, openbox run smoothly.

Does anyone have the same behavior or it is just me?

gameslayer commented on 2021-05-11 04:27 (UTC) (edited on 2021-05-11 04:29 (UTC) by gameslayer)

Download link for deb package needs to be updated.

Preparing...
Cloning chrome-remote-desktop build files...
Checking chrome-remote-desktop dependencies...
Synchronizing package databases...
Warning: paper-icon-theme-git: local (832.aa3e8af7-1) is newer than community (746.04115106-1)
Resolving dependencies...
Checking inter-conflicts...

Building chrome-remote-desktop...
==> Making package: chrome-remote-desktop 89.0.4389.85-1 (Tue 11 May 2021 14:24:36)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading chrome-remote-desktop-89.0.4389.85.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0  1449    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_89.0.4389.85_amd64.deb
    Aborting...
Failed to build chrome-remote-desktop

jamonterrell commented on 2021-05-04 04:57 (UTC) (edited on 2021-05-04 04:59 (UTC) by jamonterrell)

To get this working on recent builds, you can:

  1. git clone the git URL above
  2. Edit PKGBUILD and...
  3. ...update pkgver to be "current"
  4. ...change source URL to "${pkgname}-${pkgver}.deb::https://dl.google.com/linux/direct/${pkgname}_${pkgver}_amd64.deb"
  5. ...add this additional command with the other installs: install -Dm644 "${srcdir}/lib/systemd/system/${pkgname}@.service" "${pkgdir}/usr/lib/systemd/system/${pkgname}@.service"
  6. run updpkgsums to update the package checksums
  7. run makepkg -s to build
  8. run pacman -U *.zst to install

armanleftarm commented on 2021-05-03 13:17 (UTC)

ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb -desktop_89.0.4389.45_amd64.deb Aborting...

godlike73 commented on 2021-05-03 02:31 (UTC)

.deb link is broken as new version is out

mchan commented on 2021-05-01 23:34 (UTC) (edited on 2021-05-02 08:08 (UTC) by mchan)

I was able to install the package after manually updating the version number + checksum. However, after finishing crd --setup, I'm seeing this failure when trying to setup remote access:

[mchan@arch ~]$ DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="code here" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=arch
Enter a PIN of at least six digits: 
Enter the same PIN again: 
[0502/080736.090955:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing.
[0502/080736.190457:WARNING:host_config.cc(54)] Failed to read /home/mchan/.config/chrome-remote-desktop/host#d6194c68fcc7e79bb57401be603cb1cc.json
[0502/080736.321906:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing.
[0502/080737.709006:ERROR:daemon_controller_delegate_linux.cc(101)] Failed to enable unit: Unit file chrome-remote-desktop@mchan.service does not exist.

Couldn't start host.

Any suggestions?

atrimtab commented on 2021-03-26 22:12 (UTC)

BTW. If you'd like to avoid a (default) 2.5 minute extra wait on shutdown as systemd waits for the chrome-desktop-service to shut down. DO NOT enable or start as a service when you install per these instructions:

To {enable,start} the service, issue the command: systemctl --user {enable,start} chrome-remote-desktop

At shutdown Systemd gets stuck and eventually times out waiting for this service to exit.

DanieleMDN commented on 2021-03-02 15:43 (UTC)

It works fine, but I don't understand why the luminosity of the screen (in the main device, not in the remote one) decreases by its own while I'm using it. Does anyone has the same problem?

curlywei commented on 2021-02-05 19:31 (UTC) (edited on 2021-02-05 19:31 (UTC) by curlywei)

chrome-remote-desktop-88.0.4324.33.deb This link seems failed.

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/

nightuser commented on 2020-12-03 16:39 (UTC)

It gives 404 because Google keeps only the latest version of the package. Changing the link to latest isn't right: the version of the package and the actual version of the program wouldn't match. You can find the actual version using a command in PKGBUILD right above build() function. The commented one that starts with 'curl ...'.

Crupanshu commented on 2020-12-02 19:44 (UTC)

The source download fails with a 404. Please update the package.

andrej commented on 2020-11-12 20:23 (UTC)

The source download fails with a 404 at the moment, but that may be just transient.

miwarin commented on 2020-11-12 03:06 (UTC) (edited on 2020-11-12 03:06 (UTC) by miwarin)

I try use https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb. but I have error in makepkg. Do you have any advice?

% cd ~/.cache/yay/chrome-remote-desktop
% git diff
diff --git a/PKGBUILD b/PKGBUILD
index 5f38deb..2d8102e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,13 +14,13 @@ license=("BSD")
 depends=("gtk3" "libxss" "nss" "python2-psutil" "xorg-server-xvfb" "xorg-setxkbmap" "xorg-xauth" "xorg-xdpyinfo" "xorg-xrandr")
 install="${pkgname}.install"
 source=(
-  "${pkgname}-${pkgver}.deb::https://dl.google.com/linux/${pkgname}/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_amd64.deb"
+  "${pkgname}-${pkgver}.deb::https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb"
   "${pkgname}.service"
   "pamrule"
   "crd"
 )
 sha256sums=(
-  "63afef7bb034af9ea1b18a7026cce9f128b63339024e19f69dcf8bc87696027f"
+  "3d0055cf8db589d1bc6eb6504791d141e7008fb34cdb85bd1d194893c7d1d061"
   "e5da5ae89b5bc599f72f415d1523341b25357931b0de46159fce50ab83615a4b"
   "fcc38269eb1cc902abff9688eda9377a22367e39b9f111f87c0dd8e77adb82e2"
   "27dee2d383e6bd993fe0557d5c222fa80ab6d16d43775dedff6218713c7a1c06"
% mkdir -p src/etc/pam.d src/etc/init.d
% makepkg
==> Making package: chrome-remote-desktop 87.0.4280.27-1 (Thu Nov 12 12:03:57 2020)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found chrome-remote-desktop-87.0.4280.27.deb
  -> Found chrome-remote-desktop.service
  -> Found pamrule
  -> Found crd
==> Validating source files with sha256sums...
    chrome-remote-desktop-87.0.4280.27.deb ... Passed
    chrome-remote-desktop.service ... Passed
    pamrule ... Passed
    crd ... Passed
==> Extracting sources...
  -> Extracting chrome-remote-desktop-87.0.4280.27.deb with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
==> Entering fakeroot environment...
==> Starting package()...
cp: cannot stat '/home/miwa/.cache/yay/chrome-remote-desktop/src/etc/*': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

commented on 2020-11-12 02:20 (UTC)

Try updating the download url to https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

miwarin commented on 2020-11-11 07:23 (UTC)

Is the latest version 87.0.4280.47? https://chromereleases.googleblog.com/2020/11/beta-channel-update-for-desktop.html

The Beta channel has been updated to 87.0.4280.47 for Windows, Mac and Linux.

Has 87.0.4280.27 been deleted?

curl: (22) The requested URL returned error: 404 
==> ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_87.0.4280.27_amd64.deb
    Aborting...
error downloading sources: chrome-remote-desktop

sampsoncrowley commented on 2020-11-08 17:30 (UTC)

The current version isn't supported anymore, and returns a 404, please update to 87.0.4280.27 (63afef7bb034af9ea1b18a7026cce9f128b63339024e19f69dcf8bc87696027f)

j.taala commented on 2020-11-08 09:26 (UTC)

Gives 404 when attempting to download the package (looks like source has moved).

jkrage commented on 2020-08-07 18:32 (UTC)

Seconding @oofnik, dependency on python2-psutil should be replaced with python-psutil. Otherwise ModuleNotFoundError: No module named 'psutil' when crd is run.

Workaround of course is to install the new dependency.

crunk1 commented on 2020-07-27 17:33 (UTC)

Same as luluprat, version 85.0.4183.14 leads to a 404. Changing the version to 85.0.4183.39 and the sha256 sum to fb6afa2f771110a369ddffa39be968e7b50b0dba26093b6ca907c8f55de1317b works.

luluprat commented on 2020-07-26 18:30 (UTC)

can't install because of the following error : Erreur lors du téléchargement de https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_85.0.4183.14_amd64.deb Abandon…

ayushdutta321 commented on 2020-07-21 19:58 (UTC)

Hi, so i tried generating a code several times, then I changed to Arcolinux. the I noticed that I had to un-comment both the lines in .chrome-remote-desktop. Here is the link to the file.

https://imgur.com/4coJpp1.png

alpha7024 commented on 2020-07-17 16:19 (UTC)

When trying to install from Package Manager I'm getting the following error: curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_84.0.4147.39_amd64.deb Aborting... Failed to build chrome-remote-desktop

oofnik commented on 2020-07-03 12:56 (UTC)

I think python-psutil should be listed as a dependency now that the CRD script has been refactored to use Python 3.

gphilippi commented on 2020-06-25 16:36 (UTC)

@ayushdutta321 weird. I created an access code right now on the "remote support" tab that I said before. I don't understand why it's not working there.

I honestly don't know what may be causing the problem. Sorry. Have you tried to reinstall the package?

ayushdutta321 commented on 2020-06-25 06:33 (UTC)

@gphillippi Yeah i have the chrome remote desktop extension installed. I can connect to my friends pc using his generated code but I am unable to generate my own code. Its prompting me to download a .deb file. No terminal is not necessary

gphilippi commented on 2020-06-19 15:28 (UTC)

@ayushdutta321 to do this, I usually use the link "https://remotedesktop.google.com/access" and access the "remote support" tab. Remember to install the remote chrome desktop extension in the chrome browser.

You need a command line to do it?

ayushdutta321 commented on 2020-06-18 20:29 (UTC)

I have successfully started crd using crd --start after following steps by @victorbrca and I am also able to connect to the pc but only when both of the pc has the same gmail account signed it.

How to generate the crd remote support code and access the pc from any pc ?

gphilippi commented on 2020-05-28 16:00 (UTC)

Please, someone pins the comment of @victorbrca.

This resume all the process for using rcd.

Thanks @frealgagu, @Brinsky, @nightuser and @victorbrca.

wreckabum commented on 2020-05-20 01:57 (UTC)

After following @brinsky 's comment, It seems like audio comes out from my host machine only. Anyone having the same issue?

thibaultmol commented on 2020-05-18 22:04 (UTC)

@frealgagu @brinsky 's comment should be pinned https://aur.archlinux.org/packages/chrome-remote-desktop/?O=20&PP=10#comment-719586 it's essential for getting CRD to work

commented on 2020-04-27 14:40 (UTC)

@nightuser that's awesome thanks for that!

However I can't seem to get that working it doesn't seem to be picking up that Xsession file in /chrome-remote-desktop/. Do I just copy and paste into the Xsession file that I created and remove the + and - signs? I tried it with the + and - signs as well.

Sorry for the noob questions.

commented on 2020-04-27 14:18 (UTC)

@nightuser ah that's awesome thanks!!

I was still having issues getting it working so I blew away my config and package and re-installed but now I'm getting that it can't read my .json config. So now I'm back at square one lol.

nightuser commented on 2020-04-25 08:37 (UTC) (edited on 2020-04-25 08:39 (UTC) by nightuser)

@snipes040 Display 20 is the correct behavior. CRD on Linux starts a new Xorg session instead of the existing one. If you still want to use display 0, see my patch below. It's a bit dirty and doesn't support sound forwarding yet, but, if anyone's interested, I may rewrite it slightly and add the missing features.

commented on 2020-04-23 13:17 (UTC)

Anybody having issues getting this working after updating chrome?

My chrome version is 81.0.4044.122. I see that it's trying to use display number 20 which isn't correct but I changed the display number to 0 and it still fails.

This is what shows up in my log file.

[0423/085635.588957:INFO:host_config_upgrader.cc(125)] Requesting token exchange. [0423/085635.685608:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing. [0423/085635.806379:INFO:host_config_upgrader.cc(148)] No exchange needed, writing new config to mark as upgraded. [0423/085635.815692:INFO:host_config_upgrader.cc(191)] Successfully written host config. 2020-04-23 08:56:35,818:INFO:Using host_id: b56e140d-e5f4-118a-f566-204d28327e9c 2020-04-23 08:56:35,818:INFO:Launching X server and X session. 2020-04-23 08:56:35,826:INFO:Starting Xvfb on display :20 xdpyinfo: unable to open display ":20". The XKEYBOARD keymap compiler (xkbcomp) reports:

Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server 2020-04-23 08:56:36,334:INFO:X server is active. The XKEYBOARD keymap compiler (xkbcomp) reports: Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server 2020-04-23 08:56:36,387:INFO:Launching X session: ['/bin/sh', '/home/snipes/.chrome-remote-desktop-session'] 2020-04-23 08:56:36,389:INFO:Launching host process 2020-04-23 08:56:36,389:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/snipes/.config/chrome-remote-desktop/pulseaudio#3b58159e54/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.snipes.ssh_auth_sock', '--signal-parent'] Session output: /home/snipes/.chrome-remote-desktop-session: line 5: /usr/bin/startkde: No such file or directory 2020-04-23 08:56:36,398:INFO:wait() returned (15630,32512) 2020-04-23 08:56:36,398:INFO:Session process terminated [0423/085636.400338:INFO:remoting_me2me_host.cc(1696)] Starting host process: version 83.0.4103.2 2020-04-23 08:56:36,402:INFO:Failure count for 'session' is now 1 2020-04-23 08:56:36,402:INFO:Terminating X server Gdk-Message: 08:56:36.402: chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20.

nightuser commented on 2020-04-16 22:32 (UTC) (edited on 2020-04-16 22:35 (UTC) by nightuser)

So, since Google deletes old versions of the package, we can use pkgver function to generate version from the deb file.

Here's a working PKGBUILD: https://gist.github.com/nightuser/bb6aab68010a4c53e0537cfb7d7e965b

UPD: this works as a VCS package: the version is taken from pkgver() function and then the variable pkgver is overwritten by the returned value.

nightuser commented on 2020-04-16 21:54 (UTC)

They host only the latest version of the package. To know which one is the latest: curl -q https://dl.google.com/linux/chrome-remote-desktop/deb/dists/stable/main/binary-amd64/Packages | grep ^Filename. This is taken from Gentoo's PKGBUILD for chrome-remote-desktop package.

nightuser commented on 2020-04-16 21:52 (UTC) (edited on 2020-04-16 22:04 (UTC) by nightuser)

@sanerb They didn't change it. The latest URL looks like https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_83.0.4103.2_amd64.deb

sanerb commented on 2020-04-16 20:50 (UTC)

looks like it's 404ing for the .deb. i tried checking to see if there's a new version but either they entirely changed their directory structure or they serve a 404 on a GET to the directory it's in.

moshi commented on 2020-04-07 11:34 (UTC)

How do i enable audio ??

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.

nightuser commented on 2020-03-22 14:51 (UTC)

Also, this patch adds an option to use the existing session (but it's disable by default for compatibility reasons).

https://gist.github.com/nightuser/2ec1b91a66ec33ef0a0a67b6c570eb40

To enable it, create ~/.config/chrome-remote-desktop/Xsession file with a proper session number (usually 0 or 1).

Unfortunately, I don't yet know how to transfer sound in this case (it'll probably require enabling public pulseaudio config).

nightuser commented on 2020-03-22 13:47 (UTC) (edited on 2020-03-22 13:49 (UTC) by nightuser)

@frealgagu: Please, use the direct links to the versioned packages instead of the latest one. Fixed PKGBUILD: https://gist.github.com/nightuser/bb6aab68010a4c53e0537cfb7d7e965b ).

They have the following format:

"https://dl.google.com/linux/${pkgname}/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_amd64.deb"

nightuser commented on 2020-03-22 13:32 (UTC)

Maybe we should run

/opt/google/chrome-remote-desktop/chrome-remote-desktop --size="${crd_size}" --start

with exec?

Also, the checksum changed again.

OdinEidolon commented on 2020-03-13 20:12 (UTC)

My issue was fixed: I also needed to uncomment the DBUS line in the .chrome-remote-desktop-session file. However, the systemd service does not work. It times out after a couple of minutes:

mar 13 19:35:55 sofia-pc systemd[831]: chrome-remote-desktop.service: Failed with result 'timeout'.
mar 13 19:35:55 sofia-pc systemd[831]: Failed to start "Chrome Remote Desktop host daemon".

Funny thing, while it is still working, CRD works fine, and it also works fine if I manually issue crd --start. Any idea?

OdinEidolon commented on 2020-03-13 16:43 (UTC)

It seems I can't get this working, neither with the online nor with the headless installation modes. The package builds fine, but when I try to start crd the session cannot start:

Launching X server and X session.
Starting Xvfb on display :20
X server is active.
Launching X session: ['/bin/sh', '/home/cestino/.chrome-remote-desktop-session']
Launching host process
['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/cestino/.config/chrome-remote-desktop/pulseaudio#2293cd462a/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.cestino.ssh_auth_sock', '--signal-parent']
wait() returned (397849,256)
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 (397848,256)
Waiting before relaunching

I use KDE and configured CRD to start using startplasma-x11, as it should be. Any idea on how to proceed?

frealgagu commented on 2020-03-06 17:18 (UTC)

@ansonx10 you're right, it's the way Windows and MAC behave. I don't want to affect users who have already installed, therefore, if most users prefer to have the current session, I will make the change. I want to know if there are reasons to use a different session instead of the current one.

ansonx10 commented on 2020-03-02 21:36 (UTC)

@frealgagu Well Chrome Remote Desktop users that come from other platforms, i.e. Windows and Mac, would expect it to behave the same way on Linux. (It lets you control your existing "session" on Windows and macOS) It would be more useful for me to be able to control my existing session by default. I can't personally think of a reason that I'd need to access my own computer in a new session, and in fact, creating a new session can cause problems for some software. Using VNC is always an option regardless, but the simplicity of remote connections in CRD is nice. In the spirit of simplicity (with the target demographic in mind), I'd advocate for current session being the default.

frealgagu commented on 2020-02-10 14:40 (UTC)

@Bakasura It's nice but I'm not sure what is the expected behavior for most users. Do you think you want to use always the active session or you want to open a new session instead? I think chrome-remote-desktop developers use the :20 in order to not affect the current session

Terence commented on 2020-02-08 22:44 (UTC)

@Bakasura nice!

Bakasura commented on 2020-02-08 17:17 (UTC)

@Terence I created a patch file https://pastebin.com/tjWkgMqq

@frealgagu can you add?

Tutorj commented on 2020-01-10 12:50 (UTC)

Unable to install due to: Validating source files with sha256sums...chrome-remote-desktop-79.0.3945.10.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build chrome-remote-desktop

Any help with this? I've read the other comments that say this but I'm new and don't understand what is happening. I install Manjaro for the first time yesterday. Thanks for any help!!

kngwyu commented on 2019-12-15 16:44 (UTC)

@Brinsky It works, thanks a lot.

delamare commented on 2019-12-08 16:21 (UTC)

/usr/bin/crd launches nano. I suggest that either nano be made a dependency for this package or crd be patched to use the $EDITOR variable and check for the $EDITOR's existence before running it.

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

wreckabum commented on 2019-11-23 06:45 (UTC)

Thanks a lot! it works great after some settings. I'll write down the steps for any newbie. - build and install the package. - run crd --setup. - edit /home/user/.chrome-remote-desktop-session (remove the "#" to enable exec DE). - run crd --restart.

dirtbag commented on 2019-11-22 23:44 (UTC)

new version works.. thanks!

Terence commented on 2019-11-22 18:26 (UTC)

@frealgagu would you mind patching it with https://researchxuyc.wordpress.com/2014/07/30/to-show-the-same-display-session-in-ubuntu-by-chrome-remote-desktop/comment-page-1/ so we can use our existing session ?

dirtbag commented on 2019-11-19 21:51 (UTC)

==> Validating source files with sha256sums... chrome-remote-desktop-78.0.3904.41.deb ... FAILED chrome-remote-desktop.service ... Passed pamrule ... Passed crd ... Passed ==> ERROR: One or more files did not pass the validity check!

:(

wreckabum commented on 2019-11-19 06:36 (UTC)

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 (UTC)

Failed validity check today.

baatochan commented on 2019-09-10 08:42 (UTC) (edited on 2019-09-10 08:46 (UTC) by baatochan)

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 (UTC)

@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 (UTC)

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 (UTC)

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.

commented on 2019-08-15 18:45 (UTC)

@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 (UTC)

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

commented on 2019-08-15 14:48 (UTC)

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?

commented on 2019-08-15 14:47 (UTC)

So how are we suppose to install this package? I love this package and it worked on my (now broken install) but on my fresh install it fails the validity test and it can't be installed now.

frealgagu commented on 2019-08-13 03:38 (UTC)

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

apepa commented on 2019-08-13 00:38 (UTC)

@frealagu I know you still need to download a package, but the package as is on AUR no longer works for fresh installations, hence why I flagged as out of date.

The google page instructs you to install the .Deb and follow the instructions to set the machine up as a host. The AUR package installs the old app leaving you with no way of using it as a host with the new web based system.

frealgagu commented on 2019-08-12 22:41 (UTC)

@apepa you still need to download and install a package (.deb). This package downloads and converts to pacman for archlinux installation. Please don't flag this as outdated because is not.

apepa commented on 2019-08-11 11:41 (UTC)

No use installing the package, it just tells you the app is no longer supported and to use the new web app instead.

mrlamud commented on 2019-06-21 01:50 (UTC) (edited on 2019-06-22 06:14 (UTC) by mrlamud)

[Solved] Giving support via Incognito mode or disable Ublock Origin works well .

Problem: Giving support connected but no remote desktop appears. I have no problem getting support.

Any suggestion, will be appreciated.

leledumbo commented on 2019-06-07 17:18 (UTC)

I can confirm @zhtlancer solution works, no need to relogin/reboot. Just make that file, then crd --start will work.

kikrim commented on 2019-05-13 11:01 (UTC)

@zhtlancer is right. I have solved daemon start by creating a file chrome-remote-desktop with that content in /etc/pam.d/

Thank you very much.

franzaudio commented on 2019-05-11 15:40 (UTC) (edited on 2019-05-11 16:13 (UTC) by franzaudio)

hi all, I have a similar problem as osjacky430

on "crd --restart" I get:

The daemon is not currently running [0511/180613.232155:INFO:remoting_user_session.cc(691)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190511_180613_NJ17ss' [0511/180613.232976:WARNING:remoting_user_session.cc(613)] Failed to read from message pipe. Please check log to determine host status.

it looks like no matter what I try to start the service CRD status is always "stopped".

osjacky430 commented on 2019-03-28 13:07 (UTC) (edited on 2019-03-28 13:08 (UTC) by osjacky430)

Hi, I can't get the crd to enable remote connection, connect to others or share this computer by enter the code do work, but when I pressed enable remote connection, and enter the PIN number, my computer's name do show up in the list, but just appear to be offline.

Also,

crd --start gives me `[0328/210609.180501:INFO:remoting_user_session.cc(691)] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190328_210609_g6ApDa' 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_20190328_210609_g6ApDa`

But I got permission denied FATAL:remoting_user_session.cc(262)] [PAM] Account check: Authentication failure

I've done what @zhtlancer said, but the issue still persists.

ignapk commented on 2019-03-23 20:56 (UTC)

If anyone wants to use the current xsession (display: 0) you can follow the answer here https://superuser.com/questions/778028/configuring-chrome-remote-desktop-with-ubuntu-gnome-14-04/850359#850359 (from MDMower) I also had to add an extra pam rule to get it working, like @zhtlancer said

zhtlancer commented on 2019-03-08 02:17 (UTC) (edited on 2019-03-08 02:22 (UTC) by zhtlancer)

Recent update of PAM subsystem caused failing start of chrome-remote-desktop on my system. Add an extra pam rule for chrome-remote-desktop fixed it. This should be included in the package. Create "/etc/pam.d/chrome-remote-desktop" with following content:

auth        required    pam_unix.so
account     required    pam_unix.so
password    required    pam_unix.so
session     required    pam_unix.so

mazieres commented on 2019-02-28 17:58 (UTC)

This package works fine on machines where I've already set up sharing. However, the web app won't let me share from new machines. It keeps prompting me to install the host package and having me download the .deb file, even through I have already installed this package from AUR.

How do I convince the web app that I have installed this already so that it can generate a host#...json file for me? (Really frustrating that I have to go through this clunky web app just to generate a single file, but that's how Google seems to have designed it.)

aztec102 commented on 2019-01-16 16:39 (UTC) (edited on 2019-01-16 16:39 (UTC) by aztec102)

systemctl --user enable chrome-remote-desktop
Failed to connect to bus: Нет такого файла или каталога

I need help.

Wernight commented on 2019-01-11 08:49 (UTC)

I also see:

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

I'm more familiar with GitHub regarding sending a pull-request; I understand it's not great having to maintain frequent changes.

bdefore commented on 2018-12-08 15:26 (UTC)

I ran into similar errors as other comments with not being able to connect after entering a PIN. In looking into log files I could see errors for :20 display. This appeared to be fixed by pacman -S xorg-xrandr. This got me partway - the Manjaro device showed 'started', but the only thing showing up in clients was an error due to 'Unable to contact settings server'. I discovered that contrary to the comment in ~/.chrome-remote-desktop-session I needed to uncomment both lines, so that I had:

export $(dbus-launch)
exec startxfce4

I was then able to see the Manjaro desktop on the remote client.

frealgagu commented on 2018-11-17 20:56 (UTC)

@mradi have you found the way to use it in :0 display ?

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

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?

wcrawf commented on 2018-03-09 23:30 (UTC) (edited on 2018-03-09 23:42 (UTC) by wcrawf)

Latest package appears to be broken.

sed -e '1 s/python/python2/'

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chrome-remote-desktop#n41

This is present again, breaking /opt/google/chrome-remote-desktop/chrome-remote-desktop

After fixing that issue, I get a mysterious error:

/opt/google/chrome-remote-desktop/user-session not installed setuid root. Host must be started by administrator.

Any ideas on fixing this?

EDIT: Ah, starain's patch still isn't in. chmod +s opt/google/chrome-remote-desktop/user-session is missing from PKGBUILD as well.

mtorromeo commented on 2018-03-05 09:33 (UTC) (edited on 2018-03-05 09:34 (UTC) by mtorromeo)

Please version the source deb replacing this: source_x86_64=("<http://dl.google.com/linux/direct/>${pkgname}_current_amd64.deb")

with this: source_x86_64=("${pkgname}_${pkgver}_amd64.deb::<http://dl.google.com/linux/direct/>${pkgname}_current_amd64.deb")

so we don't have checksum fails at every update due to the deb being already present from an older release.

Thanks

klepz commented on 2018-03-04 22:25 (UTC)

Morganamilo, fixed.

Morganamilo commented on 2018-03-04 22:01 (UTC)

chrome-remote-desktop_current_amd64.deb checksums fail for me.

BlackLotus89 commented on 2018-02-10 22:01 (UTC) (edited on 2018-02-10 22:01 (UTC) by BlackLotus89)

sed -e '1 s/python/python2/'

became unnecessary and actually breaks the script

AuR commented on 2018-01-27 17:28 (UTC)

Thanks for the starain's patch.

pogtastic commented on 2018-01-16 15:08 (UTC)

Confirming that starain's patch works perfectly. Thank you very much.

acutbal commented on 2018-01-02 17:44 (UTC)

Hello, I also have the same problem:

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Hubo fallos durante la descarga de http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_61.0.3163.20_amd64.deb Cancelando...

Cheers. :D

fulgor commented on 2017-12-22 21:00 (UTC)

I have this error the link to the deb package is not found

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_61.0.3163.20_amd64.deb

arafey commented on 2017-12-16 20:52 (UTC)

@1ace: I just transferred the package to you.

1ace commented on 2017-12-15 11:43 (UTC)

@DaveB: I'm willing to adopt this package if you don't want to maintain it anymore :)

On top of the other comments people already posted, the current makedepends=('nano') is incorrect as well: the current script uses nano as runtime, not during the build, so it would be a normal depends, but it shouldn't enforce nano anyway, but instead use $EDITOR, thus dropping nano from any kind of depends.

m3thodic commented on 2017-12-10 01:08 (UTC)

@starain I forked your gist, added some deps and also enforced suid bit to user only. For anyone having issues, try using this gist in place of /opt/google/chrome-remote-desktop/chrome-remote-desktop: https://gist.github.com/tonylambiris/d9b37f224b166a823eb8115911114019

You will just have to change DEFAULT_SIZES to your regular resolution you run X at. You may also have to change FIRST_X_DISPLAY_NUMBER to share your desktop like you normally would want to in a remote pc session. I found this by running sudo xdpyinfo | head -3 (running with sudo is intentional).

Lastly, I matched .config/chrome-remote-desktop/Size to reflect the resolution set in DEFAULT_SIZES. This file literally is 1 line with 3840x2160 in it. I believe that's everything to get you up and running.

starain commented on 2017-12-10 00:03 (UTC) (edited on 2017-12-10 00:12 (UTC) by starain)

Got it work, not sure how to make it to AUR, here is the patch: https://gist.github.com/starain/d4a413826cd957384a2bbc744c4325c5

Ziul commented on 2017-12-08 00:58 (UTC)

Got the latest one from https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb, the actual md5sum is a933a425339b7d5da9dcb71fca15611f. Replaced this on the PKGBUILD. Installed ok, but got the following error when try crd --start:

/opt/google/chrome-remote-desktop/user-session not installed setuid root. Host must be started by administrator.

And this when tried with sudo:

Please run this as a normal user!

cswl commented on 2017-11-20 13:04 (UTC)

Anyone has updated PKGINFO?

DaveB commented on 2017-11-14 10:24 (UTC)

@ben0mega The problem won't be so much the AUR workflow, that's relatively easy to get into, but the new version has additional security features which I couldn't get to work. Probably a missing dependency or something, but I couldn't find it.

ben0mega commented on 2017-11-14 03:02 (UTC)

The current version is 63.0.3239.17 And can be found here: https://chrome.google.com/webstore/detail/chrome-remote-desktop/gbchcmhmhahfdphkhkmpfmihenigjmpp?hl=en I would adopt it, but I don't know what that all entails (I do write code, but I am not familiar with the Arch/AUR workflow).

niels1995 commented on 2017-11-03 16:27 (UTC)

I get a download error when trying to install this package curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Downloading failed http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_61.0.3163.20_amd64.deb Aborting...

DaveB commented on 2017-11-01 12:54 (UTC)

I'm not using this package anymore. There's quite a big update on it upstream with various bits and pieces that need seeing to and I don't have the time for it, so I'm letting the package go. CRD will need to be changed apart from anything else.

zehph commented on 2017-10-18 22:35 (UTC)

It is presenting this weird issue if you try to install it with aura, it says the CRD says it's dependant on catalyst-server, I tryed yaourt and entered the PKGBUILD editor, made no modifications and continued the build process... Installed flawlessly.

DaveB commented on 2017-10-17 20:15 (UTC)

@Bittersourness Sorry, I've only tested it using XFCE and Cinnamon on Linux to Linux. Sound is often a problem using CRD.

Bittersourness commented on 2017-10-17 08:34 (UTC) (edited on 2017-10-17 08:36 (UTC) by Bittersourness)

I have no sound from my linux box, "apparently" there is no sound device (and the sound icon is crossed in the taskbar). However, there IS a sound card, and it works when I use my linux box in person :P Using x2go I get sound with a recognized device named "Wave Out on Microsoft Sound assigner" (maybe it's a bad translation from spanish and not the real message you can get, sorry) Does anyone knows what could be the problem? Maybe related with pulseaudio? Or a configuration problem (maybe permissions) in Windows? By the way, I'm connecting to a Manjaro desktop with KDE from Windows 10. And it happens to me since the beginning, it's not related to the last CRD update.

DaveB commented on 2017-10-16 11:33 (UTC)

@Pallegro thanks for the heads up

pallegro commented on 2017-10-15 15:27 (UTC)

fyi, this depends on gtk3 instead of gtk2 now

DaveB commented on 2017-09-19 13:45 (UTC)

Thanks :) There shouldn't be a resource difference since either method does much the same thing, but autostarting using systemd may run some single-instance programs in the CRD session that you'd want to use in your native desktop session.

annoyingduck commented on 2017-09-19 02:30 (UTC)

Bravo on this package, makes installing a breeze. 2 questions: is there a big resource difference between autostarting via systemctl --user enable chrome-remote-desktop.service or adding crd to the startup applications? 2nd: on Windows there is a clear notification that the desktop is being accessed/actions can be seen on the target computer screen, but not on Linux (there is zero indication that another computer is accessing the target machine). Anyone come up with a way to tell if your computer is being accessed via crd?

DaveB commented on 2017-06-02 21:00 (UTC)

Done. What a messy update. Thanks for alpha and beta testing, spider-mario and Zeroedout.

spider-mario commented on 2017-06-01 21:57 (UTC)

Also, I think the new line: echo "export $(dbus-launch)" >> ... should use single quotes, not double quotes.

Zeroedout commented on 2017-06-01 17:58 (UTC)

MD5sum failed on crd. "... crd ... FAILED ..."

kokeroulis commented on 2017-05-26 18:43 (UTC)

I am trying to install the crd and i am seeing the following error, https://gist.github.com/anonymous/8adc4167794ff363a549a0781aa28147 does anyone know how i can fix this? The package xorg-xrandr is installed and the version is 1.5.0-1

DaveB commented on 2017-05-23 07:58 (UTC)

PSA: Chrome Remote Desktop is not part of the Google Chrome package. The CRD versions lag behind.

Kuchiriel commented on 2017-05-09 04:48 (UTC)

Someone please create an openrc package of this!

DaveB commented on 2017-04-11 10:27 (UTC)

Thanks @Bittersourness!

Bittersourness commented on 2017-04-11 09:17 (UTC) (edited on 2017-04-11 09:19 (UTC) by Bittersourness)

If anyone is having trouble with dbus and KDE with a message like this (FYI @grayjoc): dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead startkde: Could not sync environment to dbus. You have to add "export $(dbus-launch)" before startkde in ~/.chrome-remote-desktop-session: # You will have to uncomment one of the following lines for CRD to work # Remove the # and select ctrl-X to finish. # export $(dbus-launch) exec /usr/bin/startkde # exec /usr/bin/openbox-session # exec /usr/bin/openbox-kde-session And that's it, you will see your desktop like a boss! :D

mold commented on 2017-04-10 20:11 (UTC)

Appears to have 404d as of today.

MRogalla commented on 2017-04-06 22:02 (UTC)

There is a missing dependency: xorg-xrandr. Without it, I got the following error: xdpyinfo: unable to open display ":20". After installing it via pacman, CRD works for me.

DaveB commented on 2017-03-22 08:01 (UTC)

@dgerdem There could be any number of reasons for that, CRD is gnarly and not at all easy to set up. I doubt dbus is the actual problem as it usually catches all the problems that go before it. Check that your firewall isn't blocking it, check that your host system is allowing connections, see whether it works on another client, such as a Chrome/Chromium instance on the host system itself... Sorry I can only offer the general advice you've probably tried ten times already.

dgerdem commented on 2017-03-22 02:35 (UTC)

I'm kind of new to the Arch world. I'm trying to CRD working to enable remote access to my newly installed, up to date Manjaro installation. I got CRD installed, registered with my google account. Once CRD is started and I attempt to connect to it from an android phone, I get a black screen on the phone with a message box saying "Unable to contact settings server. Failed to connect to socket /tmp/dbus-(random letters): connection refused. Once I close that, it says unable to load failsafe session. I pasted the log below. Above the stunport.cc messages in the full log, it shows that the service is ready to accept connections, and it shows my connection attempt. Thanks! [0321/212425.631805:WARNING:stunport.cc(385)] Jingle:Port[0x30e97e530800::0:0:stun:Net[enp3s0:2600:8803:8403:x:x:x:x:x/64:Unknown]]: StunPort: stun host lookup received error 0 [0321/212425.636820:WARNING:stunport.cc(385)] Jingle:Port[0x30e97e530800::0:0:stun:Net[enp3s0:2600:8803:8403:x:x:x:x:x/64:Unknown]]: StunPort: stun host lookup received error 0 [0321/212425.639156:WARNING:stunport.cc(385)] Jingle:Port[0x30e97e6dac00::0:0:stun:Net[enp3s0:2600:8803:8403:x:x:x:x:x/64:Unknown]]: StunPort: stun host lookup received error 0 [0321/212425.664385:WARNING:basicportallocator.cc(724)] Discarding candidate because port is already done gathering. [0321/212425.672509:WARNING:basicportallocator.cc(724)] Discarding candidate because port is already done gathering. (xfce4-session:3741): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-D8BzAiZun8: Connection refused (xfce4-session:3741): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-D8BzAiZun8: Connection refused (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed gpg-agent[3825]: WARNING: "--write-env-file" is an obsolete option - it has no effect gpg-agent: a gpg-agent is already running - not starting a new one (xfce4-session:3741): xfce4-session-WARNING **: gpg-agent returned no PID in the variables (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /home/admin/.cache/sessions/xfce4-session-AVARICE:20, Does it exist? Permissions issue? (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed 2017-03-21 21:24:32,471:INFO:wait() returned (3733,0) 2017-03-21 21:24:32,471:INFO:Session process terminated 2017-03-21 21:24:32,472:INFO:Terminating X server chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20. chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20. 2017-03-21 21:24:32,477:INFO:wait() returned (3705,0) 2017-03-21 21:24:32,477:INFO:X server process terminated 2017-03-21 21:24:32,477:INFO:Failure count for 'X server' is now 1 2017-03-21 21:24:32,478:INFO:Launching X server and X session. 2017-03-21 21:24:32,488:INFO:Starting Xvfb on display :20 2017-03-21 21:24:32,536:INFO:X server is active. 2017-03-21 21:24:32,589:INFO:Launching X session: ['/bin/sh', '/home/admin/.chrome-remote-desktop-session'] 2017-03-21 21:24:32,591:INFO:wait() returned (3734,256) 2017-03-21 21:24:32,591:INFO:Host process terminated 2017-03-21 21:24:32,591:INFO:Failure count for 'host' is now 1 2017-03-21 21:24:32,591:INFO:Host exited with status 1. 2017-03-21 21:24:32,592:INFO:Launching host process 2017-03-21 21:24:32,592:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/admin/.config/chrome-remote-desktop/pulseaudio#90e20e57fa/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.admin.ssh_auth_sock', '--signal-parent'] /usr/bin/startxfce4: X server already running on display :20 [0321/212432.605764:INFO:remoting_me2me_host.cc(1614)] Starting host process: version 56.0.2924.51 xrdb: "Xft.hinting" on line 19 overrides entry on line 6 xrdb: "Xft.hintstyle" on line 22 overrides entry on line 7 [0321/212432.623156:INFO:remoting_me2me_host.cc(1248)] Policy does not require curtain-mode. [0321/212432.623177:INFO:remoting_me2me_host.cc(1173)] Policy enables NAT traversal. [0321/212432.623187:INFO:remoting_me2me_host.cc(1191)] Policy enables use of relay server. [0321/212432.623193:INFO:remoting_me2me_host.cc(1212)] Policy restricts UDP port range to: <no port range specified> [0321/212432.623201:INFO:remoting_me2me_host.cc(1266)] Policy sets talkgadget prefix: chromoting-host [0321/212432.623211:INFO:remoting_me2me_host.cc(1275)] Policy sets third-party token URLs: <no 3rd party auth config specified> [0321/212432.623218:INFO:remoting_me2me_host.cc(1297)] Policy enables client pairing. [0321/212432.623223:INFO:remoting_me2me_host.cc(1313)] Policy enables security key auth. [0321/212432.623240:INFO:remoting_me2me_host.cc(558)] Processing new host configuration. [0321/212432.737159:INFO:chromoting_host.cc(107)] Starting host [0321/212432.739044:INFO:remoting_me2me_host.cc(1062)] Policy sets host domain: [0321/212432.739050:INFO:remoting_me2me_host.cc(1146)] Policy does not require host username match. [0321/212433.738170:INFO:dns_blackhole_checker.cc(60)] Verifying connection to https://chromoting-host.talkgadget.google.com/talkgadget/oauth/chrome-remote-desktop-host [0321/212433.933210:INFO:dns_blackhole_checker.cc(38)] Successfully connected to host talkgadget. [0321/212433.933236:INFO:signaling_connector.cc(184)] Attempting to connect signaling. [0321/212433.933243:INFO:oauth_token_getter_impl.cc(159)] Refreshing OAuth token. [0321/212434.210045:INFO:oauth_token_getter_impl.cc(55)] Received OAuth token. [0321/212434.210057:INFO:signaling_connector.cc(124)] Received user info. [0321/212434.714752:INFO:signaling_connector.cc(72)] Signaling connected. New JID: 590a80cb4d57f460503b32c6cc0abe0a@chromoting.gserviceaccount.com/chromoting835C7A47 [0321/212434.953906:INFO:remoting_me2me_host.cc(881)] Host ready to receive connections. 2017-03-21 21:24:34,954:INFO:Host ready to receive connections.

DaveB commented on 2017-03-17 08:42 (UTC)

@grayjoc Sorry, can't help – I don't use KDE, so I can't test the error

grayjoc commented on 2017-03-11 21:27 (UTC)

@DaveB Hi, I'm currently experiencing the following errors when starting crd. When I try to connect remotely I get the last error message in an X window "could not sync environment to dbus". ... 2017-03-11 21:20:16,308:INFO:Starting Xvfb on display :20 xdpyinfo: unable to open display ":20". ... [0311/212016.907903:INFO:remoting_me2me_host.cc(558)] Processing new host configuration. startkde: Starting up... dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead startkde: Could not sync environment to dbus.

DaveB commented on 2017-02-01 10:18 (UTC)

Stupid stupid mistake. Fixed now.

DaveB commented on 2017-02-01 10:09 (UTC)

@Bittersourness I'm having the same issue, build works locally but not from AUR. I'm trying to fix it.

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.

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.

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)

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

DaveB commented on 2016-12-04 22:02 (UTC)

PLEASE READ THIS BEFORE YOU UPDATE There have been significant changes in this release that I can't trace back. The server should work (tested here), but I can't guarantee compatibility with your browser (especially if it's Chromium) or with your DE. If you're using v5.2 and you're happy with it, please stick to it or keep a backup of the old version until you're sure the new one works. Google has removed the old version from the servers.

DaveB commented on 2016-11-19 08:22 (UTC)

@Mike, it's the out of date issue.

MikeW50 commented on 2016-11-18 20:51 (UTC)

I'm getting the error: curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_52.0.2743.74_amd64.deb Aborting... while running makepkg. Is this the out of date issue, or should I be looking for a different problem?

DaveB commented on 2016-11-18 19:35 (UTC) (edited on 2016-11-18 19:49 (UTC) by DaveB)

I'm going to leave it at this version and mark it out of date until Chromium is updated. I'm guessing that Chromium's outdated Native Client is one of the problems, and until that's updated, there isn't much I can do. ETA: pnacl isn't it, I tried c/p-ing the chrome version into it – didn't work.

commented on 2016-11-18 10:32 (UTC)

@DaveB No problem man, take your time. It's not critical for me. Mainly use it for my homeserver, but will use VNC for the time being. Is Chrome also v52 when you tried it? Version differences between chrome & chrome remote desktop might explain downgrade issues.

DaveB commented on 2016-11-18 10:15 (UTC) (edited on 2016-11-18 10:21 (UTC) by DaveB)

@Timo That'S right, the package has been deleted upstream. I only downgraded it to prevent other users attempting to upgrade and getting an error. I've reinstalled 52 and it doesn't seem to be working anymore with chrome (I get into the machine but session won't start) or chromium (complains that NaCl isn't working, but I suspect there's another problem that I'll have to look into). I'm trying to get 55 to work again, same deal. The pnacl version in Chromium is older than in Chromium. That might explain things. Doesn't solve your problem though.

commented on 2016-11-18 09:35 (UTC)

@DaveB Thanks for the quick response! Seems that something went wrong with downgrading since now I get a error 404 when trying to install through pacaur (pacakge v52 not available anymore?) Pastebin of error log http://pastebin.com/WxvuDD4X

DaveB commented on 2016-11-18 07:35 (UTC)

@Timo Thanks, I just tried running CRD 55 myself (stupid stupid didn't check to see whether it would actually *run*, only install) and got into a mass of problems. The problem seems to be upstream. I'm not sure whether there's an actual problem upstream or CRD has been changed and now only works on Debian/Ubuntu machines, but finding out will cost too much time and this is the kind of software people rely on to get work done. I've downgraded the AUR package so that it actually works for the time being. Many thanks for the feedback and sorry for the inconvenience.

commented on 2016-11-17 14:06 (UTC)

@DaveB Apologies for not responding after the last question, but yes after restarting the server, I got it right ;). Now facing another problem :(: After the latest update, I cannot start the chrome-remote-desktop service anymore. Xvfb says that it cannot open display :20... Previous version worked fine, only happening now that I did a -Syu with pacaur. Complete reinstall of both google-chrome & chrome-remote-desktop packages after purging config files also did not help Pastebin of error log http://pastebin.com/GMcXgH51

DaveB commented on 2016-11-12 15:27 (UTC)

@Timo, have you started up the server?

commented on 2016-11-06 17:42 (UTC)

Anyone else having the problem that the "enable remote connections" button is not visible in chrome?

DaveB commented on 2016-08-16 23:26 (UTC)

@kcolford Added for next update.

kcolford commented on 2016-08-16 20:58 (UTC)

Could you add the -r option when groupadd is invoked? It seems a little silly to see gid 1001 being used by chrome-remote-desktop

DaveB commented on 2016-07-03 05:22 (UTC) (edited on 2016-07-03 05:23 (UTC) by DaveB)

Bztwy: Nope, I use XFCE on the host and client. Gnome looks problematic, someone else had problems with it.

Bztvuy commented on 2016-07-02 17:39 (UTC)

Have any of you managed to make it work with gnome 3? I've tried everything I've found about this online and the best I got was a black screen with an X in the middle that crashes after a few seconds.

mradi commented on 2016-05-10 14:17 (UTC)

These steps helped me, took me a while to figure out so here to record them Setup Steps: Install Chrome-remote-desktop 1. crd --setup 2. Enable chrome-remote-desktop from browser (and do crd --enable from command line while it is trying to set it up) 3. Optional: To get display 0 working https://productforums.google.com/forum/#!topic/chrome/LJgIh-IJ9Lk

DaveB commented on 2016-04-23 19:03 (UTC) (edited on 2016-08-17 00:23 (UTC) by DaveB)

@caleb You might have a good argument, but I still think that you can deal with the extra dependency of using nano than others dealing with vi. It's one thing to have to face an editor that is prehistoric to most users, it's another to expect them how to find out how to use it during a complex install, or interrupt the install to sort out the editor. ETA: Ok, if and when I get around to it (probably on the next update), I'll try and remember to include an option to select between nano and the default editor. But understand that I'm not putting a high priority on this. ETA2: Ok I've re-reconsidered, and the answer is still no. Nano is in the core, so it should be in any arch installation unless someone actually decides to uninstall it for whatever reason. Including it as a dependency is more of a fail-safe than anything. The argument as to what "anybody running arch" is a really big assumption on your part, or did you take a survey? It is possible to install and run arch without thinking about or needing to change the $EDITOR or $VISUAL variables on a permanent basis. "Knowing roughly what's going on" isn't enough to use vi, and certainly not while installing a complex piece of software. Adding an option to change the editor would add more unnecessary complexity. The only reason vi is the default editor in Arch or any other distro I know of is probably because it's POSIX standard, which has no relevance here at all and doesn't bind anyone else to anything. Most text installers including Linux distros themselves that require editing use something other than vi because vi is a pig to use if you don't already use it as your standard editor on a regular basis. The advantages of usability for more unsophisticated Arch users – and I've aimed this package so anyone can install it with a minimum of trouble, otherwise I wouldn't have bothered with the .install and CRD scripts – far outweigh any actual advantages there might be (I can't think of any) of effectively leaving it at vi. If you can provide any real benefits from using the $EDITOR/$VISUAL or real disadvantages in requiring nano, I'd be more than willing to reconsider. Until then, my decision to use nano is final.

alerque commented on 2016-04-23 12:21 (UTC)

@DaveB Please reconsider @dlh's request. I came here to request the same thing. Anybody running Arch is already going to have $EDITOR setup and at least one thing setup on their system. Yes this usually defaults to vi, but again anybody that setup Arch is going to know roughly what's going on. If they want to change that at the system level to another editor of their choosing they can, but forcing some other editor as a dependency for some package that has nomething to do with editing is not a good solution. Your preferences not agreeing with Arch's system defaults isn't enough reason to hoist that decision on all downstream users of a package.

DaveB commented on 2016-04-01 07:42 (UTC)

Unfortunately, there doesn't seem to be an i686 version anymore, getting a 404 error from the direct link and the download page. Will update as and when there is a 32-bit version available.

DaveB commented on 2016-03-02 21:46 (UTC)

@dlh I'm leaving it at nano, as setting up nano as a default editor is a pain and I don't want to subject anyone to vi as the default editor if they just want to install this package.

dlh commented on 2016-02-29 21:07 (UTC)

@DaveB: You should not require nano, but instead invoke editor that is specified in EDITOR env variable.

DaveB commented on 2016-02-25 22:05 (UTC)

ephemient: Done, thanks for your help!

ephemient commented on 2016-02-25 20:45 (UTC)

Could you change @@ -16,3 +16,3 @@ -_arch=i386 -[ "$CARCH" == x86_64 ] && _arch=amd64 -source=("https://dl.google.com/linux/direct/${pkgname}_current_${_arch}.deb" +source_i686=("http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_i386.deb") +source_x86_64=("http://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_amd64.deb") +source=( @@ -21 +21,3 @@ -md5sums=('SKIP' +md5sums_i686=('bf9135f439fa4bfa1daf16e96c62d87a') +md5sums_x86_64=('90cd272f1758617478380906f5cbc219') +md5sums=( please? Using _current.deb breaks for those of us caching with /etc/makepkg.conf:SRCDEST and there's no reason not to include checksums.

Det commented on 2015-12-16 12:48 (UTC)

"cd "$srcdir"" is redundant.

DaveB commented on 2015-12-08 22:07 (UTC)

Det, could you please stop flagging this out of date? I check it every day, it is up to date.

DaveB commented on 2015-11-30 14:43 (UTC)

You're welcome :)

Paviluf commented on 2015-11-30 12:21 (UTC)

Yes problem solved. At least there is some useful info on the comments about this now. Sorry for the inconvenience Dave and thank you for your work ;)

DaveB commented on 2015-11-30 06:14 (UTC) (edited on 2015-11-30 08:38 (UTC) by DaveB)

I'm not going to do that, as it would involve providing support for Google's product and open up a whole new channel of sorrow and pain and wasted Sunday afternoons. That's not specifically aimed at you Jeremy. I can't provide support for CRD itself as that would involve keeping track of CRD and that changes Google might make to it, which would involve constantly installing and uninstalling CRD and the permissions in the browser and everything or I run the serious risk of giving outdated info. I just don't have the time to do that, and I don't have to as CRD itself is not my product to provide support for. It's outside my jurisdiction. I have to assume that people using CRD are able to follow the instructions provided by Google, even if that assumption obviously won't withstand the reality test. Other than that, can I assume that the problem is solved?

Paviluf commented on 2015-11-30 03:14 (UTC)

Ok I found the problem. There 2 part in CRD "remote access" and "my computer". It's in the "my computer" that you needed to enable the access. I only had enabled the access at the first launch when the prompt ask to it... I don't see that explained. I hope this will be helpful for others and keeps people off the back of the great but not so patient DaveB ;) Thanks I guess. Ps. DaveB if you really don't want anybody asking questions maybe you should add this info to the message at the end of the scprit ?

DaveB commented on 2015-11-29 23:46 (UTC)

The crd script works, but you have to enable CRD in your browser first or it won't. I've said that several times here, you should have seen it in the post-install notes, during the setup routine or the first thing in the help if you'd bothered to look there. But ok, the missing file error wasn't exactly helpful so I've updated the script with a more meaningful error message. I don't really believe in masking error messages but if it keeps people off my back, so be it.

Paviluf commented on 2015-11-29 20:15 (UTC)

It's not if I'm happy or not, I just want to make it works ;) I first posted to be sure that what I was doing was OK and because other people had the same error. I thought we could clear some things. I have the error message I showed you with the crd command with CRD access enabled (you mean the first time you launch chrome remote desktop in chrome when it ask you the authorization right ?) After I enabled the CRD access the first time I launched chrome remote desktop in chrome I don't have to enabling or disabling it again after that. For me and others the crd command don't seems to works. Ps. I had an error with "sudo systemctl --user enable chrome-remote-desktop" but I saw that we have to use this command as a normal user (no sudo / no root).

DaveB commented on 2015-11-29 16:24 (UTC) (edited on 2015-11-29 17:20 (UTC) by DaveB)

If you're getting that error message, it's because you haven't yet enabled CRD access to the internet in your browser. Which is a bit like trying to print something without switching the printer on. The server will then obviously not run, and will return that message. As I said before, if you're happy enabling and disabling CRD in the browser to start or kill the server, please, do that. It's probably even somewhat more secure than using the crd method or "systemctl --user start...", but I doubt the added security makes up for the inconvenience (and potential problems with screen res, pulse... etc.), at least for me. But as always, your installation, your machine, your scenario, you do whatever you want with it. "systemctl --user enable chrome-remote-desktop" starts the server at login. That's good if your host machine is only intended for use as a server without other peripherals attached, such as a server you have running on its own in the basement. Run as a desktop, you will run into conflicts with single-instance processes running in the server session but not in the desktop session. You can also call "crd --start" from start-up in your session manager with the exact same effect. "systemctl --user start chrome-remote-desktop" calls the Google chrome-remote-desktop script in the /opt directory in a very roundabout way, but does exactly the same thing as "crd --start", only "crd --start" gives you additional benefits (the pulse mess, screen resolution) that I didn't want to include in the systemd service. Simply typing "crd [--start]" is a little easier than typing out "systemctl --user start chrome-remote-desktop" or enabling connections to the internet from the browser every time you want to start the server, wouldn't you agree? Especially if you have to go somewhere with a client machine and just want to fire up the server before you leave, which is my usual usage scenario. There is no "always have to" in this. Please just use it whichever way you want, whatever suits your usage scenario. Are there any actual questions, recommendations or improvements you would like to put forward to me? I'm not sure where you're trying to go with this.

Paviluf commented on 2015-11-29 14:24 (UTC)

What I mean is that if you run crd you will have an error and it will not start as you can see in previous comments : CRD is not running; starting. Deleting old pulse audio files Failed to load config: [Errno 2] No such file or directory: '/home/jeremy/.config/chrome-remote-desktop/host#<removed hash>.json' 2015-11-29 15:06:56,822:INFO:Cleanup. Is there something wrong with crd that produce this error ? I just found that it seems to works without the need to use crd. I should have say that is for a "on demand" use and not for an always running chrome-remote-desktop server. If one want it to always run you have to use this I think ? systemctl --user {enable,start} chrome-remote-desktop

DaveB commented on 2015-11-29 13:51 (UTC) (edited on 2015-11-29 14:06 (UTC) by DaveB)

@Paviluf, That's all you need to get it set up and running initially, but how you continue using the Chrome Remote Desktop server depends entirely on how you want to use it. I can't speak for anyone else, but I only have the server running when I know I'll need it. Ok I suppose you can also allow and disallow the server in Chrome or Chromium every time you want to switch the server on or off, but that has its own problems – your preferred screen resolution for the client might be ignored, and old pulse config files probably won't work (though I don't know, that might have been fixed since I wrote the crd script). And possibly other problems, I don't know, I haven't tried using it like that. I just find it more convenient just to use the crd script, which is why I wrote it. Chrome Remote Desktop isn't like most applications that you run while sitting in front of the machine you're running the application on. This involves inherent and potentially serious security risks that neither Google nor anyone else can avoid, and only the user can mitigate. I can't predict all possible usage scenarios, much less test them. So if you find that ignoring crd and crd --start works for you, that's great, use it that way, but I can't tell you whether you'll be happy with that particular use or not. To avoid confusion, I only wrote the crd script, the package itself is from Google and was written for Ubuntu. I only repackaged it for Arch.

Paviluf commented on 2015-11-29 11:42 (UTC) (edited on 2015-11-29 14:22 (UTC) by Paviluf)

If I understand correctly we just have to do that to make Chrome remote desktop works : $ yaourt -S chrome-remote-desktop $ crd --setup - Follow the instructions - Start Chrome remote desktop in your chrome or chromium browser (you need to be connected to your Google account) and enable access when asked. - That's all ! Are these parts are optional ? crd --start (or 'crd') systemctl --user {enable,start} chrome-remote-desktop Thanks

DaveB commented on 2015-11-22 11:49 (UTC) (edited on 2015-11-22 11:51 (UTC) by DaveB)

@dlh To check and, if necessary, adjust config files on setup.

dlh commented on 2015-11-22 11:14 (UTC)

Why you need nano as dependencie?

DaveB commented on 2015-10-30 15:53 (UTC)

Hey, that's right... You have to allow the chromium/chrome client to access the internet on the local machine before you can run the server

Raansu commented on 2015-10-30 12:56 (UTC) (edited on 2015-10-30 13:03 (UTC) by Raansu)

Hi, I ran 'crd --setup' as my non-root user with no apparent error then when I ran 'crd --restart' I got the following error. [raansu@Y40-80 ~]$ crd --restart The daemon is not currently running Failed to load config: [Errno 2] No such file or directory: '/home/raansu/.config/chrome-remote-desktop/host#<removed hash, maybe security reasons?>.json' 2015-10-30 05:53:28,203:INFO:Cleanup. [raansu@Y40-80 ~]$ EDIT: same thing with 'crd --start' or just 'crd' EDIT2: Tried running it anyway from Chromium and it worked, was able to connect using the Chrome Remote Desktop app on my android tablet.

DaveB commented on 2015-10-16 05:34 (UTC) (edited on 2015-10-16 05:41 (UTC) by DaveB)

Not sure who flagged this package out of date, but it isn't. The host version IS the latest on the google server. The client (on chrome/chromium) is already at 46, but that's the client, not the host.

DaveB commented on 2015-10-07 19:58 (UTC)

Should work now. I've tried to make the installation messages and setup routine more helpful.

journcy commented on 2015-10-07 01:50 (UTC) (edited on 2015-10-07 01:53 (UTC) by journcy)

"Failed to load config: [Errno 2] No such file or directory: '/home/<user>/.config/chrome-remote-desktop/host#<long hash of unknown purpose>.json'" I installed this package from the AUR, ran "crd --setup", and then ran "crd --start". I get the above error message. Also, this: "gpasswd: group 'chrome-remote-desktop' does not exist in /etc/group" ...happens during "crd --setup".

DaveB commented on 2015-10-05 12:46 (UTC) (edited on 2015-10-06 08:50 (UTC) by DaveB)

If you find that your sound isn't working, it's probably because of two alterations to /etc/pulse/client.conf and /etc/pulse/daemon.conf. Restore them to their defaults, restart pulse, and you should get sound on the client as well. It might still sound ragged though, so don't expect miracles. I'll add this note to the next package. Also, it's _not_ a good idea to autostart CRD – some programs are single-instance, and won't start on the machine running CRD if they're already running in the CRD instance. One example is AutoKey.

DaveB commented on 2015-10-05 09:19 (UTC) (edited on 2015-10-05 09:42 (UTC) by DaveB)

Ok, tried it again. Turned out a little more complicated than I thought. Also added "crd" command for starting and stopping chrome-remote-desktop from the command line, also destroys old and useless pulse audio files where necessary as they don't work between sessions. crd has a --setup option as manually adding bits and pieces after the install is inconvenient.

WhiteHatHacker1 commented on 2015-10-02 18:33 (UTC)

@DaveB, yes. I did have two .json files already in my chromium native-messaging-hosts directory. They're named "com.google.chrome.remote_assistance.json" and "com.google.chrome.remote_desktop.json" but appear to be symlinks which makes me wonder whether a previous version of the package made them.

DaveB commented on 2015-10-01 08:26 (UTC)

Thanks @WhiteHatHacker1! I don't use chromium, so I'm tapping in the dark. This is an aspect of packaging I don't know much about – I'll have to look into it over the weekend. I'll probably solve it using a find-xargs one-liner. If the file is already in there, the attempt to ln -s it will fail anyway, but that may or may not have nasty repercussions on uninstalling so I'll have to look into it. Question though – were one or two of the the same .json files already in your chromium native-messaging-hosts directory?

WhiteHatHacker1 commented on 2015-09-28 21:02 (UTC)

Thanks for adopting the package @DaveB! I think the symlink you suggested is problematic as well, @soxet. I already have the "native-messaging-hosts" directory in my "/etc/chromium" folder, so trying to create a symlink to it results in an error. Perhaps the presence of correct symlinks could be checked for before symlinking the two .json files individually.

DaveB commented on 2015-09-27 14:11 (UTC)

Hey, I've adopted the package. This is going to be one of those high-maintenance Google packages, so if you see anything you think needs fixing or if you have any suggestions, please comment here – or even better, send me an e-mail. I'd like to keep this package healthy, so any help will be welcome. If anyone else wants to take over the package, I'd be only too happy to surrender it.

soxet commented on 2015-09-09 22:11 (UTC)

/etc/chromium/native-messaging-hosts contains a * file which is a symlink. This doesn't work. Need to replace dir with correct symlink: ln -s /etc/opt/chrome/native-messaging-hosts/ native-messaging-hosts

noderat commented on 2015-09-03 09:33 (UTC)

Current version is 45.0.2454.17, you need to bump the version number to force an AUR update!

DaveB commented on 2015-07-23 15:11 (UTC)

Hey, the current version is 44.0.2403.44 – you might want to update the PKGBUILD to force an AUR update.

DaveB commented on 2015-06-12 16:58 (UTC)

Oh. Then I have no clue, sorry.

Binero commented on 2015-06-12 16:54 (UTC)

I can run multiple instances of gnome-session inside different ttys.

DaveB commented on 2015-06-12 16:49 (UTC)

Oh wait... you mean it would segfault inside chrome on the client machine's gnome-session instance? Sounds like gnome-session doesn't like being in two instances... not sure if not a deal breaker, but if not, you might want to try another DE?

DaveB commented on 2015-06-12 16:46 (UTC)

Hm... chrome shouldn't run the server, you have to start that manually (or via systemd, or in some other way on the host machine)... if you want to do something with CRD in chrome, you should already have CRD server running on your machine... I can't remember how I set it up, I only remember there was some sequence of things I had to do and if I didn't get it right, I'd get segfaults.

Binero commented on 2015-06-12 16:41 (UTC)

gnome-session just segfaults when Chrome runs it for me.

DaveB commented on 2015-06-12 16:37 (UTC)

Hey Binero, Yep, google packages are a real pain. I managed to find some on a web repository with version numbers instead of "current", but not all of them are there and it defeats the point of using hashes if you're downloading them from 3rd-party sources. I don't use systemd or any other autostart for CRD – it would "grab" some single-instance progs I have running at autostart so they wouldn't run on my host, so I start CRD on an as-needed basis using a shell script (does one or two other things as well, like deleting the old pulse audio session and forcing CRD to create a new one, old ones didn't work). You shouldn't need to reference a DM – I have "exec startxfce4" in my ~/.chrome-remote-desktop-session. I use lxdm as a DM, no problems – though a running GDM instance might complain for some reason.

Binero commented on 2015-06-12 14:48 (UTC)

@DaveB Ideally the PKGBUILD would just get the version from the package. Anyway, I am trying to set this up with GDM/gnome-session, but having a bit of trouble. Do you happen to know how this is done? (not using lightdm)

DaveB commented on 2015-06-12 14:26 (UTC)

The current version I have installed is now 41.0.2272.41-1 $ ./chrome-remote-desktop --host-version 41.0.2272.41 At the time I wrote my PKBUILD (which is now out of date), the AUR version was still 38.xxx (if I remember right), and was throwing out-of-date warnings on guests. The current package seems up to date and checks out at the current version, but the version number stated in the PKGBUILD is old?

Binero commented on 2015-06-12 12:45 (UTC)

@DaveB How is this out of date? It always gets the latest one.

DaveB commented on 2015-03-28 14:55 (UTC)

Very out of date – current version is 40.0.2214.115. This is my PKGBUILD: pkgname=chrome-remote-desktop pkgver=40.0.2214.115 pkgrel=1 pkgdesc="Allows you to securely access your computer over the Internet through Chrome." url="https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp" arch=('i686' 'x86_64') license=('BSD') install=$pkgname.install depends=('python2' 'python2-psutil' 'gconf' 'gtk2' 'nss' 'xorg-xdpyinfo' 'xorg-setxkbmap' 'xorg-server-xvfb' 'xorg-xauth') source=("chrome-remote-desktop.service") md5sums=('cde1758e875ff114cc8153edb7087d2a') _arch=i386 if [ "$CARCH" == i686 ]; then md5sums+=('02963cacf89532849160df219676b05f') elif [ "$CARCH" == x86_64 ]; then _arch=amd64 md5sums+=('bbd835e485306b9be76c4d8555d5a6ea') fi source+=(${pkgname}_${pkgver}_$_arch.deb::https://dl.google.com/linux/direct/${pkgname}_current_$_arch.deb) package() { msg2 "Extracting data.tar.gz" bsdtar -xf data.tar.gz -C "$pkgdir/" msg2 "Patching Python script" sed -e '1 s/python/python2/' \ -e '/^.*sudo_command =/ s/"gksudo .*"/"pkexec"/' \ -e '/^.*command =/ s/s -- sh -c/s sh -c/' \ -i "$pkgdir"/opt/google/chrome-remote-desktop/chrome-remote-desktop msg2 "Removing things that won't work" rm -R "$pkgdir"/etc/cron.daily/ rm -R "$pkgdir"/etc/init.d/ rm -R "$pkgdir"/etc/pam.d/ msg2 "They forgot the LICENSE file, using the copyright file instead" install -Dm644 "$pkgdir"/usr/share/doc/$pkgname/copyright "$pkgdir"/usr/share/licenses/$pkgname/copyright msg2 "Adding a systemd user service" install -Dm644 "$srcdir"/$pkgname.service "$pkgdir"/usr/lib/systemd/user/$pkgname.service msg2 "Creating symlinks for chromium compatibility" mkdir -p "$pkgdir"/etc/chromium/native-messaging-hosts ln -sr "$pkgdir"/etc/opt/chrome/native-messaging-hosts/* "$pkgdir"/etc/chromium/native-messaging-hosts } I haven't tested the 386 version, but it should work.

WhiteHatHacker1 commented on 2015-03-13 18:06 (UTC)

I order to get my install working, I did what @mobabur94 typed (+1 for great instructions), but I had to do something a little different for the symlink. Because I already had another program that created the native-messaging-hosts directory, I couldn't link "/etc/opt/chrome/native-messaging-hosts/" to "/etc/chromium". Instead, I did this: "ln -s /etc/opt/chrome/native-messaging-hosts/* /etc/chromium/native-messaging-hosts/", in addition to deleting the link already there named "*".

mobabur94 commented on 2015-03-12 20:04 (UTC)

In order to get it working: 1. I manually created the chrome-remote-desktop group, and added myself to it. 2. I manually created the ~/.chrome-remote-desktop-session file with "exec startxfce4" in it. 3. I manually created the ~/.config/chrome-remote-desktop directory. 4. I manually changed the symlink for chromium using: "ln -s /etc/opt/chrome/native-messaging-hosts/ /etc/chromium" (@ishitatsuyuki is right) Also, I never used systemctl to start or enable the chrome-remote-desktop service; if I am not mistaken, the extension is supposed to invoke the python script. After all that, I was able to get it to show the "Enable remote connections" button. Clicking that button generates the host json file in ~/.config/chrome-remote-desktop. Now, connecting from another computer successfully starts xfce. But it starts it on :20, not :0, which I guess is expected, since the python script tries to get "a candidate display number for which there is currently no x server lock file". Although, it logs in using my user, chromium within the remote connection uses a blank profile, which gets created in ~/.config/chrome-remote-desktop/chrome-profile. I haven't tried to symlink that to ~/.config/chromium because the python script suggests to sign in and sync. I am not sure why remote assistance is allowed to use :0 while remote desktop needs to use :20... Perhaps package maintainer can fix the symlink and the groupadd.

ishitatsuyuki commented on 2015-02-22 02:48 (UTC)

Linking * seems to do wrong thing. It make a link named \*.

7i7o commented on 2015-01-15 05:11 (UTC)

You should list xorg-xrandr as a dependency. Line 425 of the google-remote-desktop service script calls xrandr and throws an exception when not installed (had a REALLY light desktop with no need for extra xorg-server-utils and couldn't start service because of that). Installed it and voila! Remote desktop up and running (took me a couple of hours to discover it since i'm not a debug-friendly kind of guy.

camio commented on 2015-01-08 00:15 (UTC)

When installing I received the following error "groupadd: invalid group ID 'chrome-remote-desktop'". I'm not sure how critical this is.

agnotek commented on 2014-12-23 16:49 (UTC)

use this PKGBUILD: # Maintainer: Mateus Rodrigues Costa <charles [dot] costar [at] gmail [dot] com> pkgname=chrome-remote-desktop pkgver=40.0.2214.44 pkgrel=2 pkgdesc="Allows you to securely access your computer over the Internet through Chrome." url="https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp" arch=('i686' 'x86_64') license=('BSD') install=$pkgname.install depends=('python2' 'python2-psutil' 'gconf' 'gtk2' 'nss' 'xorg-xdpyinfo' 'xorg-setxkbmap' 'xorg-server-xvfb' 'xorg-xauth') source=("chrome-remote-desktop.service") md5sums=('cde1758e875ff114cc8153edb7087d2a') _arch=i386 if [ "$CARCH" == i686 ]; then md5sums+=('8cf84e5801c3b5c6cff0a9efb2b1ba6a') elif [ "$CARCH" == x86_64 ]; then _arch=amd64 md5sums+=('03aaba1f91dbd1da367dc3ff4e0c5c3a') fi source+=(${pkgname}_${pkgver}_$_arch.deb::https://dl.google.com/linux/direct/${pkgname}_current_$_arch.deb) package() { msg2 "Extracting data.tar.gz" bsdtar -xf data.tar.gz -C "$pkgdir/" msg2 "Patching Python script" sed -e '1 s/python/python2/' \ -e '/^.*sudo_command =/ s/"gksudo .*"/"pkexec"/' \ -e '/^.*command =/ s/s -- sh -c/s sh -c/' \ -i "$pkgdir"/opt/google/chrome-remote-desktop/chrome-remote-desktop msg2 "Removing things that won't work" rm -R "$pkgdir"/etc/cron.daily/ rm -R "$pkgdir"/etc/init.d/ rm -R "$pkgdir"/etc/pam.d/ msg2 "They forgot the LICENSE file, using the copyright file instead" install -Dm644 "$pkgdir"/usr/share/doc/$pkgname/copyright "$pkgdir"/usr/share/licenses/$pkgname/copyright msg2 "Adding a systemd user service" install -Dm644 "$srcdir"/$pkgname.service "$pkgdir"/usr/lib/systemd/user/$pkgname.service msg2 "Creating symlinks for chromium compatibility" mkdir -p "$pkgdir"/etc/chromium/native-messaging-hosts ln -sr "$pkgdir"/etc/opt/chrome/native-messaging-hosts/* "$pkgdir"/etc/chromium/native-messaging-hosts }

txomon commented on 2014-12-17 10:00 (UTC)

md5sum for amd64 deb is c3882feb4f11eea34d7d05bc44d268c9

Stephen12 commented on 2014-11-11 10:47 (UTC)

How does it work?? https://www.apponfly.com/en/ @Brandon? Others? @CharlesAtum did jamesan finally adopt it??? I might be interested..

Brandon commented on 2014-11-10 15:54 (UTC)

I had too hard time fixing all the errors, I decided to change whole platform http://pastebin.com/6CrRF2EP does anybody have an experience?? btw:@CharlesAtum: I had similar problem as @jamesan and changing the dependencies from python 2 to 3 did not work on my PC either

agnotek commented on 2014-10-30 12:19 (UTC)

for PKGBUILD: pkgver=38.0.2125.9 _arch=amd64 md5sums+=('d5322560215d4569608b76390a4cdb4f') don't know md5sum for i686

dlh commented on 2014-10-07 07:30 (UTC)

Checksums are wrong

commented on 2014-09-18 17:19 (UTC)

@jamesan Could you take a look if CRD still works if you remove the first sed line and change the dependencies from python 2 to 3?

gyurman commented on 2014-09-15 20:53 (UTC)

How can I connect to exciting session?

jamesan commented on 2014-09-13 18:33 (UTC)

Adopted this package. Let's see..: @vendion: I left out a couple steps apparently. Before step 5, the chrome-remote-desktop user group needs to be created and the hosting user must join that group: # groupadd chrome-remote-desktop # usermod -aG chrome-remote-desktop <username> Then, step 5 should generate the expected JSON file and not throw an error after your pin entry. Then, the chrome-remote-desktop user service can be started/enabled to receive remote connection requests. I'll try to codify some of this stuff in the PKGBUILD so there aren't as many or any manual steps needed to make this work after installing the package. Stay tuned...

commented on 2014-08-29 16:50 (UTC)

Disowned, feel free to adopt it if you are interested.

vendion commented on 2014-08-29 02:04 (UTC)

@jamesan: Following you're seven step procedure I get to 5 before I run into any problems. I have created ~/.config/chrome-remote-desktop and I have "/home/vendion/gocode/bin/wingo" (this is used by Slim to start my window manager) in my ~/.chrome-remote-desktop-session file. When I click "Enable Remote Connections" and give it a pin, I get an error and the json file is never created in ~/.config/chrome-remote-desktop. Any ideas?

commented on 2014-08-28 17:19 (UTC)

I lost interest in chrome-remote-desktop and will disown it soon. Anybody interested in adopting it? Maybe jamesan?

commented on 2014-08-17 23:40 (UTC)

@jamesan I am not sure if a pkgver() function would be useful for a non development package: It would work for anyone installing the package for the first time, but I think I would still need to submit new versions so AUR helpers could detect a update. Also, The google-chrome packages maintained by Det show a way to know the new version by checking the repository metadata. There probably should be a way to do the same for CRD.

jamesan commented on 2014-08-16 12:27 (UTC)

More progress! Using the pkgver function, you can extract the debian package version from it's control file with the one-liner: pkgver() { bsdtar -xf control.tar.gz -O control | grep '^Version: ' | cut -f2 -d' ' } Observing the various Chrome/Chromium AUR packages, packages that do determine the version simply skip the checksum verification (i.e. chromium-browser-bin) allowing the PKGBUILD to perpetually track the latest release without intervention. Modified the PKGBUILD slightly to do this here: http://pastebin.com/z6tCi28F (PKGBUILD) http://pastebin.com/2qJVBVpL (PKGBUILD diff)

commented on 2014-08-16 11:57 (UTC)

@jamesan Thanks for pointing out the service error, I knew it should be under the Unit heading but I didn't pay too much attention when I was actually changing the file. The install file currently only tells the user to create ~/.config/chrome-remote-desktop, I will add something about the desktop session file.

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.

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

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.

vendion commented on 2014-07-21 11:09 (UTC)

The SystemD service seems like it is unable to load for me. I created the "~/.config/chrome-remote-desktop" enabled and started the service it fails with: Jul 21 07:04:27 Baldr systemd[823]: Starting "Chrome Remote Desktop host daemon"... Jul 21 07:04:27 Baldr chrome-remote-desktop[3530]: Failed to load config: [Errno 2] No such file or directory: '/home/vendion/.config/chrome-remote-desktop/host#d20b60e1d094abcbd6a458593874c8ed.json' Jul 21 07:04:27 Baldr chrome-remote-desktop[3530]: 2014-07-21 07:04:27,185:INFO:Cleanup. Jul 21 07:04:27 Baldr systemd[823]: chrome-remote-desktop.service: control process exited, code=exited status=1 Jul 21 07:04:27 Baldr systemd[823]: Failed to start "Chrome Remote Desktop host daemon". Jul 21 07:04:27 Baldr systemd[823]: Unit chrome-remote-desktop.service entered failed state. Infact the chrome-remote-desktop directory is empty. Anyone run into something like this, because the services fails to load I can't configure remote destktop?

phazen18 commented on 2014-07-21 00:03 (UTC)

This is starting to look like its getting in pretty good shape. For the first time, I can enable the plugin on the host side and start a session on the client side. However, it looks like its getting a broken xterm session of some kind then terminates. FWIW, I'm on Gnome. Thanks for all the effort so far. I can't wait for this to work!

commented on 2014-07-18 00:19 (UTC)

The devs made the python script compatible with both psutil versions, so I dropped the patch and got back to using sed for python 2 and pkexec support. I made some changes in the systemd service, remember that you can override it anytime at in ~/.config/systemd/user/ for your user or /etc/systemd/user/ for all users. The install script gives some more info, sorry if it's somehow annoying.

ava1ar commented on 2014-07-16 20:17 (UTC)

@thepasto Looks like connection is established, but creation session on linux side is not working. I will try to troubleshot it on VM and will post update later on. Thanks for sharing you experience.

thepasto commented on 2014-07-13 10:44 (UTC)

@ava1ar thanks for your work! here's my try. Everything seems to work as well. I can enable incoming connection on my laptop, but when i try to access from my tablet i get this error. https://drive.google.com/file/d/0B-yQDH0HYifnMXlMbG00cWk4Q3M/edit?usp=sharing

ava1ar commented on 2014-07-10 05:54 (UTC)

Few more notes: I created a patch for python2-psutils and pkexec compatibility: http://pastebin.com/JtmP5kDk Here is updated PKBDUILD, which applies this patch: http://pastebin.com/bFpb8eP8 It uses following chrome-remote-desktop.install file: http://pastebin.com/266042tB Install file required to request manual action: user should create ~/.config/chrome-remote-desktop folder manually after installation, otherwise chrome plugin won't allow to setup access. After all this action I was able to setup the access, but I failed to check it, since it currently supports only gdm/lightdm setup, but I ma using KDE. So fill free to try and share you experience!

ava1ar commented on 2014-07-10 03:37 (UTC)

Thanks for the quick update. Actually, there is another problem exists: chrome-remote-desktop requires python2-psutil of version 1.x, while only 2.x exists in Arch repos. With 2.x I am getting following exception while trying to launch it: Traceback (most recent call last): File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1210, in <module> sys.exit(main()) File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 971, in main pid = get_daemon_pid() File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 509, in get_daemon_pid except psutil.error.Error: AttributeError: 'ModuleWrapper' object has no attribute 'error' I am currently trying to patch it for version 2.x. Will post an update shortly.

ava1ar commented on 2014-07-10 02:06 (UTC)

Symlinking whole directory /opt/chrome/native-messaging-hosts to /etc/chromium/native-messaging-hosts is not a good idea. If user has something installed to /etc/chromium/native-messaging-hosts (i.e. lastpass), package will fail to install due to attempt to overwrite existing dir. Much better is symlinking of required files. Only thing you need is replace last line ln -sr opt/chrome/native-messaging-hosts chromium/native-messaging-hosts with ln -sr opt/chrome/native-messaging-hosts/* chromium/native-messaging-hosts This will symlink every individual file and avoid conflicts with other chromium addons.

sacarde commented on 2014-07-09 18:27 (UTC)

OK thanks a lot

commented on 2014-07-09 16:25 (UTC)

Ops, "systemctl --user enable chrome-remote-desktop.service"

commented on 2014-07-09 16:18 (UTC)

@sacarde It's a user service, you need to use systemd on user mode (--user) to start it. Try "systemctl --user list-unit-files" and "systemctl enable chrome-remote-desktop.service" as your own user.

sacarde commented on 2014-07-09 15:49 (UTC)

if I try: systemctl enable chrome-remote-desktop.service Failed to execute operation: No such file or directory

sacarde commented on 2014-07-09 09:45 (UTC)

hi, I dont view "chrome-remote-desktop" in "systemctl list-unit-files" is this OK ? thanks

dlh commented on 2014-06-30 06:32 (UTC)

Please update pkg to create symlink.

commented on 2014-06-25 20:05 (UTC)

Grr, I still don't get when the hell that host json file is created. Maybe creating the hashes is important for it? Also, I tried creating a systemd service for it, currently it will run in user mode, I still have to test it when I manage to create that host file. Also, about the chromium issue: You should have a symbolic link so that /etc/chromium/native-messaging-hosts redirects to /etc/opt/chrome/native-messaging-hosts. I have already created this on the next pkgrel.

jamesan commented on 2014-06-23 08:52 (UTC)

Package builds and installs without a hitch. It works only for one-time remote access and only with the CRD extension installed on Chrome. CRD installed on Chromium doesn't seem to detect that this package is installed (so doesn't execute the binaries and generate the one-time access code). Also, CRD doesn't allow for the user's DE to be registered under the persistent remoting list, probably because the host process isn't running (persistently under a service unit). Running /opt/google/chrome-remote-desktop/chrome-remote-desktop --start manually halts when it can't find the ~/.config/chrome-remote-desktop/host#SOME_HASH.json file. I can't figure out how this JSON file is created... The Feb 21, 2014 comment at: https://code.google.com/p/chromium/wiki/ChromotingBuildInstructions seems to imply that running chrome-remote-desktop --start simply works (and the JSON file is automagically generated) and provides a systemd service unit file template. Has any passed where I'm stuck here?

commented on 2014-06-07 17:48 (UTC)

Patched the python script so it uses Python 2 instead of Python 3 and pkexec instead of gksudo. I'll wait until they port to Fedora to provide the init service: https://code.google.com/p/chromium/issues/detail?id=343329

dlh commented on 2014-06-07 12:47 (UTC)

Doesn't work