Package Details: chrome-remote-desktop 77.0.3865.32-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: 104
Popularity: 2.840309
First Submitted: 2014-04-27 23:43
Last Updated: 2019-08-27 15:50

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 ... 8 9 10 11 12 13 14 15 16 17 18 ... Next › Last »

Paviluf commented on 2015-11-29 20:15

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

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

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

@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

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

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

dlh commented on 2015-11-22 11:14

Why you need nano as dependencie?

DaveB commented on 2015-10-30 15:53

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

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

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.