Package Details: chrome-remote-desktop 76.0.3809.117-1

Git Clone URL: https://aur.archlinux.org/chrome-remote-desktop.git (read-only)
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: 102
Popularity: 2.870654
First Submitted: 2014-04-27 23:43
Last Updated: 2019-08-15 21:00

Pinned Comments

frealgagu commented on 2019-08-12 22:41

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

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 12 13 14 15 ... Next › Last »

DaveB commented on 2016-11-18 19:35

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.

TimoVerbrugghe commented on 2016-11-18 10:32

@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

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

TimoVerbrugghe commented on 2016-11-18 09:35

@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

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

TimoVerbrugghe commented on 2016-11-17 14:06

@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

@Timo, have you started up the server?

TimoVerbrugghe commented on 2016-11-06 17:42

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

DaveB commented on 2016-08-16 23:26

@kcolford Added for next update.

kcolford commented on 2016-08-16 20:58

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