Package Details: chrome-remote-desktop 118.0.5993.9-1

Git Clone URL: (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:
Keywords: Chrome Chromium Google Networking Remote
Licenses: BSD
Submitter: None
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 123
Popularity: 0.184254
First Submitted: 2014-04-27 23:43 (UTC)
Last Updated: 2023-10-06 21:11 (UTC)

Pinned Comments

frealgagu commented on 2020-12-05 22:38 (UTC)

I maintain the latest built package at:

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 (

  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
  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="<>" --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

1 2 3 4 5 6 .. 32 Next › Last »

jvybihal commented on 2024-04-04 12:32 (UTC) (edited on 2024-04-04 12:34 (UTC) by jvybihal)

It is not about what I prefer. It's about what it (mis)represents. I get what you are trying to do, but this is not how it's done. You should try to work with @frealgagu and get chrome-remote-desktop updated. If he does not respond in reasonable time, and the package is not maintained, you should create orphan request and then adopt the package if accepted.

And to the PKGBUILD itself, having SKIP for the sha256sum check of the .deb file itself is WRONG and should not be done!

mvidaldp commented on 2024-04-03 22:58 (UTC)

@jvybihal I could change it to -latest if you prefer. Or merge it like you suggested :)

jvybihal commented on 2024-04-03 14:09 (UTC)

How is this -git package??

wartemw commented on 2023-10-05 08:57 (UTC)

changed the drain:

<--- "${pkgname}-${pkgver}.deb::${pkgname}/deb/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}_amd64.deb"

"${pkgname}-${pkgver}.deb::" --->


<--- "84396947d787cbe90073e944c272856871086c2671d82ac59f6ee9f460476459"

"f0471692d2f14d382259178a9d54abd53255dc528ce4ff22c50510035438cdec" --->

and commented

<--- patch -Np1 -i "${srcdir}/xdg-base-directory.patch"

patch -Np1 -i "${srcdir}/xdg-base-directory.patch"


boustanihani commented on 2023-10-04 21:47 (UTC)

curl: (22) The requested URL returned error: 404 ==> FEHLER: Fehler beim Download von Breche ab...

ciberbago commented on 2023-09-30 15:11 (UTC) (edited on 2023-09-30 15:12 (UTC) by ciberbago)

Hello! I get the following error in the final step:

curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading Aborting... error: failed to download sources for 'chrome-remote-desktop-116.0.5845.10-1': error: packages failed to build: chrome-remote-desktop-116.0.5845.10-1

frealgagu commented on 2023-08-15 00:22 (UTC)

@ewuplse01 thanks, it works like a charm.

ewuplse01 commented on 2023-08-13 22:53 (UTC) (edited on 2023-08-14 16:31 (UTC) by ewuplse01)

I created a diff for PKGBUILD that works for 116.0.5845.10

< pkgver=115.0.5790.10
> pkgver=116.0.5845.10
< depends=("gtk3" "libutempter" "libxss" "nss" "python-psutil" "xorg-server-xvfb" "xorg-setxkbmap" "xorg-xauth" "xorg-xdpyinfo" "xorg-xrandr")
> depends=("gtk3" "libutempter" "libxss" "nss" "python-psutil" "xorg-server-xvfb" "xorg-setxkbmap" "xorg-xauth" "xorg-xdpyinfo" "xorg-xrandr" "xf86-video-dummy" "python-packaging" "python-pyxdg")
<   "a49ac21281a220c17afcfdcdf4a274d1e094927aea135f53ee7eb39a2c1b07a4"
>   "84396947d787cbe90073e944c272856871086c2671d82ac59f6ee9f460476459"
>   # fix problem with missing import xdg.BaseDirectory
>   # point xorg_binary to the location that it is installed in Arch Linux
>   sed -i -r   -e 's|import xdg$|import xdg, xdg.BaseDirectory|' \
>               -e 's|xorg_binary = "/usr/lib/xorg/Xorg"|xorg_binary = "/usr/lib/Xorg"|' \
>               "${srcdir}/opt/google/chrome-remote-desktop/chrome-remote-desktop"

ewuplse01 commented on 2023-08-13 16:34 (UTC) (edited on 2023-08-14 16:59 (UTC) by ewuplse01)

@truncs I was able to successfully start chrome-remote-desktop@user.service after I modified xorg_binary (line 1447). Arch installs Xorg in /usr/lib/Xorg whereas debian installs it in /usr/lib/xorg/Xorg.

$ diff chrome-remote-desktop.orig /opt/google/chrome-remote-desktop/chrome-remote-desktop
< import xdg
> import xdg, xdg.BaseDirectory
<     xorg_binary = "/usr/lib/xorg/Xorg";
>     xorg_binary = "/usr/lib/Xorg";

truncs commented on 2023-08-11 21:56 (UTC) (edited on 2023-08-11 21:57 (UTC) by truncs)

Changing from

import xdg


import xdg, xdg.BaseDirectory

helped me resolve the error for now.

Although it leads to a new error

Aug 11 14:47:33 earth chrome-remote-desktop[355503]:   File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1409, in _wait_for_x
Aug 11 14:47:33 earth chrome-remote-desktop[355503]:     raise Exception("Could not connect to X server.")
Aug 11 14:47:33 earth chrome-remote-desktop[355503]: Exception: Could not connect to X server.
Aug 11 14:47:33 earth chrome-remote-desktop[355503]: 2023-08-11 14:47:33,352:INFO:Cleanup.