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: 122
Popularity: 0.007993
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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 32 Next › Last »

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.

journcy commented on 2015-10-07 01:50 (UTC) (edited on 2015-10-07 01:53 (UTC) by journcy)

"Failed to load config: [Errno 2] No such file or directory: '/home/<user>/.config/chrome-remote-desktop/host#<long hash of unknown purpose>.json'" I installed this package from the AUR, ran "crd --setup", and then ran "crd --start". I get the above error message. Also, this: "gpasswd: group 'chrome-remote-desktop' does not exist in /etc/group" ...happens during "crd --setup".

DaveB commented on 2015-10-05 12:46 (UTC) (edited on 2015-10-06 08:50 (UTC) by DaveB)

If you find that your sound isn't working, it's probably because of two alterations to /etc/pulse/client.conf and /etc/pulse/daemon.conf. Restore them to their defaults, restart pulse, and you should get sound on the client as well. It might still sound ragged though, so don't expect miracles. I'll add this note to the next package. Also, it's _not_ a good idea to autostart CRD – some programs are single-instance, and won't start on the machine running CRD if they're already running in the CRD instance. One example is AutoKey.

DaveB commented on 2015-10-05 09:19 (UTC) (edited on 2015-10-05 09:42 (UTC) by DaveB)

Ok, tried it again. Turned out a little more complicated than I thought. Also added "crd" command for starting and stopping chrome-remote-desktop from the command line, also destroys old and useless pulse audio files where necessary as they don't work between sessions. crd has a --setup option as manually adding bits and pieces after the install is inconvenient.

WhiteHatHacker1 commented on 2015-10-02 18:33 (UTC)

@DaveB, yes. I did have two .json files already in my chromium native-messaging-hosts directory. They're named "com.google.chrome.remote_assistance.json" and "com.google.chrome.remote_desktop.json" but appear to be symlinks which makes me wonder whether a previous version of the package made them.

DaveB commented on 2015-10-01 08:26 (UTC)

Thanks @WhiteHatHacker1! I don't use chromium, so I'm tapping in the dark. This is an aspect of packaging I don't know much about – I'll have to look into it over the weekend. I'll probably solve it using a find-xargs one-liner. If the file is already in there, the attempt to ln -s it will fail anyway, but that may or may not have nasty repercussions on uninstalling so I'll have to look into it. Question though – were one or two of the the same .json files already in your chromium native-messaging-hosts directory?

WhiteHatHacker1 commented on 2015-09-28 21:02 (UTC)

Thanks for adopting the package @DaveB! I think the symlink you suggested is problematic as well, @soxet. I already have the "native-messaging-hosts" directory in my "/etc/chromium" folder, so trying to create a symlink to it results in an error. Perhaps the presence of correct symlinks could be checked for before symlinking the two .json files individually.

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