Package Details: chrome-remote-desktop 118.0.5993.9-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: 123
Popularity: 0.24
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:

https://github.com/frealgagu/archlinux.chrome-remote-desktop/releases/

victorbrca commented on 2020-04-03 01:04 (UTC)

Thanks @frealgagu for packaging this, @nightuser for the existing session patch and @Brinsky for the instructions.

I've compiled both instructions with screenshots and added it to my blog if anyone is having issues with the install. Otherwise, just follow the instructions in the comments by @Brinsky from 2019-12-06 13:58.

Brinsky commented on 2019-12-06 13:58 (UTC)

Here's how I got this working with the new web app (remotedesktop.google.com):

  1. Build and install the package
  2. run crd --setup
  3. (Optional) Configure execution of your preferred window manager in ~/.chrome-remote-desktop-session
  4. Go to http://remotedesktop.google.com/headless
  5. Click "next" and "authorize" through each instruction
  6. Copy/paste and run the provided "Debian" command, which should look like the following: DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="<UNIQUE_CODE>" --redirect-url="<https://remotedesktop.google.com/_/oauthredirect>" --name=
  7. Set up a name and PIN
  8. Wait for successful output containing "Host ready to receive connections."
  9. Run crd --start

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 32 Next › Last »

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.

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 32 Next › Last »