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.45
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 .. 19 20 21 22 23 24 25 26 27 28 29 .. 32 Next › Last »

Paviluf commented on 2015-11-29 14:24 (UTC)

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 (UTC) (edited on 2015-11-29 14:06 (UTC) by DaveB)

@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 (UTC) (edited on 2015-11-29 14:22 (UTC) by Paviluf)

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 (UTC) (edited on 2015-11-22 11:51 (UTC) by DaveB)

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

dlh commented on 2015-11-22 11:14 (UTC)

Why you need nano as dependencie?

DaveB commented on 2015-10-30 15:53 (UTC)

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 (UTC) (edited on 2015-10-30 13:03 (UTC) by Raansu)

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 (UTC) (edited on 2015-10-16 05:41 (UTC) by DaveB)

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.

DaveB commented on 2015-10-07 19:58 (UTC)

Should work now. I've tried to make the installation messages and setup routine more helpful.

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 32 Next › Last »