The SystemD service seems like it is unable to load for me. I created the "~/.config/chrome-remote-desktop" enabled and started the service it fails with:
Jul 21 07:04:27 Baldr systemd[823]: Starting "Chrome Remote Desktop host daemon"...
Jul 21 07:04:27 Baldr chrome-remote-desktop[3530]: Failed to load config: [Errno 2] No such file or directory: '/home/vendion/.config/chrome-remote-desktop/host#d20b60e1d094abcbd6a458593874c8ed.json'
Jul 21 07:04:27 Baldr chrome-remote-desktop[3530]: 2014-07-21 07:04:27,185:INFO:Cleanup.
Jul 21 07:04:27 Baldr systemd[823]: chrome-remote-desktop.service: control process exited, code=exited status=1
Jul 21 07:04:27 Baldr systemd[823]: Failed to start "Chrome Remote Desktop host daemon".
Jul 21 07:04:27 Baldr systemd[823]: Unit chrome-remote-desktop.service entered failed state.
Infact the chrome-remote-desktop directory is empty. Anyone run into something like this, because the services fails to load I can't configure remote destktop?
Search Criteria
Package Details: chrome-remote-desktop 130.0.6723.14-1
Package Actions
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.99 |
First Submitted: | 2014-04-27 23:43 (UTC) |
Last Updated: | 2024-10-16 18:54 (UTC) |
Dependencies (13)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libutempter (libutempter-gitAUR)
- libxss
- nss (nss-hgAUR)
- python-packaging
- python-psutil
- python-pyxdg
- xf86-video-dummy (xf86-video-dummy-with-vtAUR)
- xorg-server-xvfb (xorg-server-xvfb-gitAUR)
- xorg-setxkbmap
- xorg-xauth
- xorg-xdpyinfo
- xorg-xrandr (xorg-xrandr-gitAUR)
Required by (0)
Sources (5)
Latest Comments
« First ‹ Previous 1 .. 26 27 28 29 30 31 32 Next › Last »
vendion commented on 2014-07-21 11:09 (UTC)
phazen18 commented on 2014-07-21 00:03 (UTC)
This is starting to look like its getting in pretty good shape. For the first time, I can enable the plugin on the host side and start a session on the client side. However, it looks like its getting a broken xterm session of some kind then terminates. FWIW, I'm on Gnome.
Thanks for all the effort so far. I can't wait for this to work!
<deleted-account> commented on 2014-07-18 00:19 (UTC)
The devs made the python script compatible with both psutil versions, so I dropped the patch and got back to using sed for python 2 and pkexec support.
I made some changes in the systemd service, remember that you can override it anytime at in ~/.config/systemd/user/ for your user or /etc/systemd/user/ for all users.
The install script gives some more info, sorry if it's somehow annoying.
ava1ar commented on 2014-07-16 20:17 (UTC)
@thepasto
Looks like connection is established, but creation session on linux side is not working. I will try to troubleshot it on VM and will post update later on. Thanks for sharing you experience.
thepasto commented on 2014-07-13 10:44 (UTC)
@ava1ar thanks for your work!
here's my try. Everything seems to work as well. I can enable incoming connection on my laptop, but when i try to access from my tablet i get this error.
https://drive.google.com/file/d/0B-yQDH0HYifnMXlMbG00cWk4Q3M/edit?usp=sharing
ava1ar commented on 2014-07-10 05:54 (UTC)
Few more notes:
I created a patch for python2-psutils and pkexec compatibility: http://pastebin.com/JtmP5kDk
Here is updated PKBDUILD, which applies this patch: http://pastebin.com/bFpb8eP8
It uses following chrome-remote-desktop.install file: http://pastebin.com/266042tB
Install file required to request manual action: user should create ~/.config/chrome-remote-desktop folder manually after installation, otherwise chrome plugin won't allow to setup access.
After all this action I was able to setup the access, but I failed to check it, since it currently supports only gdm/lightdm setup, but I ma using KDE. So fill free to try and share you experience!
ava1ar commented on 2014-07-10 03:37 (UTC)
Thanks for the quick update. Actually, there is another problem exists: chrome-remote-desktop requires python2-psutil of version 1.x, while only 2.x exists in Arch repos.
With 2.x I am getting following exception while trying to launch it:
Traceback (most recent call last):
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 1210, in <module>
sys.exit(main())
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 971, in main
pid = get_daemon_pid()
File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 509, in get_daemon_pid
except psutil.error.Error:
AttributeError: 'ModuleWrapper' object has no attribute 'error'
I am currently trying to patch it for version 2.x. Will post an update shortly.
ava1ar commented on 2014-07-10 02:06 (UTC)
Symlinking whole directory /opt/chrome/native-messaging-hosts to /etc/chromium/native-messaging-hosts is not a good idea. If user has something installed to /etc/chromium/native-messaging-hosts (i.e. lastpass), package will fail to install due to attempt to overwrite existing dir. Much better is symlinking of required files. Only thing you need is replace last line
ln -sr opt/chrome/native-messaging-hosts chromium/native-messaging-hosts
with
ln -sr opt/chrome/native-messaging-hosts/* chromium/native-messaging-hosts
This will symlink every individual file and avoid conflicts with other chromium addons.
sacarde commented on 2014-07-09 18:27 (UTC)
OK
thanks a lot
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):
crd --setup
~/.chrome-remote-desktop-session
DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="<UNIQUE_CODE>" --redirect-url="<https://remotedesktop.google.com/_/oauthredirect>" --name=
crd --start