Package Details: chrome-remote-desktop 61.0.3163.20-2

Git Clone URL: https://aur.archlinux.org/chrome-remote-desktop.git (read-only)
Package Base: chrome-remote-desktop
Description: Allows you to securely access your computer over the Internet through Chrome.
Upstream URL: https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp
Keywords: Chrome Chromium Google Networking
Licenses: BSD
Submitter: None
Maintainer: DaveB
Last Packager: DaveB
Votes: 81
Popularity: 2.500807
First Submitted: 2014-04-27 23:43
Last Updated: 2017-10-16 11:38

Latest Comments

zehph commented on 2017-10-18 22:35

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

@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

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

@Pallegro thanks for the heads up

pallegro commented on 2017-10-15 15:27

fyi, this depends on gtk3 instead of gtk2 now

DaveB commented on 2017-09-19 13:45

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

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

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

spider-mario commented on 2017-06-01 21:57

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

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

All comments