Package Details: chrome-remote-desktop 130.0.6723.14-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.59
First Submitted: 2014-04-27 23:43 (UTC)
Last Updated: 2024-10-16 18:54 (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 .. 21 22 23 24 25 26 27 28 29 30 31 32 Next › Last »

DaveB commented on 2015-09-27 14:11 (UTC)

Hey, I've adopted the package. This is going to be one of those high-maintenance Google packages, so if you see anything you think needs fixing or if you have any suggestions, please comment here – or even better, send me an e-mail. I'd like to keep this package healthy, so any help will be welcome. If anyone else wants to take over the package, I'd be only too happy to surrender it.

soxet commented on 2015-09-09 22:11 (UTC)

/etc/chromium/native-messaging-hosts contains a * file which is a symlink. This doesn't work. Need to replace dir with correct symlink: ln -s /etc/opt/chrome/native-messaging-hosts/ native-messaging-hosts

noderat commented on 2015-09-03 09:33 (UTC)

Current version is 45.0.2454.17, you need to bump the version number to force an AUR update!

DaveB commented on 2015-07-23 15:11 (UTC)

Hey, the current version is 44.0.2403.44 – you might want to update the PKGBUILD to force an AUR update.

DaveB commented on 2015-06-12 16:58 (UTC)

Oh. Then I have no clue, sorry.

Binero commented on 2015-06-12 16:54 (UTC)

I can run multiple instances of gnome-session inside different ttys.

DaveB commented on 2015-06-12 16:49 (UTC)

Oh wait... you mean it would segfault inside chrome on the client machine's gnome-session instance? Sounds like gnome-session doesn't like being in two instances... not sure if not a deal breaker, but if not, you might want to try another DE?

DaveB commented on 2015-06-12 16:46 (UTC)

Hm... chrome shouldn't run the server, you have to start that manually (or via systemd, or in some other way on the host machine)... if you want to do something with CRD in chrome, you should already have CRD server running on your machine... I can't remember how I set it up, I only remember there was some sequence of things I had to do and if I didn't get it right, I'd get segfaults.

Binero commented on 2015-06-12 16:41 (UTC)

gnome-session just segfaults when Chrome runs it for me.

DaveB commented on 2015-06-12 16:37 (UTC)

Hey Binero, Yep, google packages are a real pain. I managed to find some on a web repository with version numbers instead of "current", but not all of them are there and it defeats the point of using hashes if you're downloading them from 3rd-party sources. I don't use systemd or any other autostart for CRD – it would "grab" some single-instance progs I have running at autostart so they wouldn't run on my host, so I start CRD on an as-needed basis using a shell script (does one or two other things as well, like deleting the old pulse audio session and forcing CRD to create a new one, old ones didn't work). You shouldn't need to reference a DM – I have "exec startxfce4" in my ~/.chrome-remote-desktop-session. I use lxdm as a DM, no problems – though a running GDM instance might complain for some reason.

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