Arch Linux chrome remote desktop

4 minutes ago, Lemon797 said:

I installed it on the user account how do I fix it? I deleted tigervnc and all the files you told me to make.

su root, to login as root. Then just follow the instructions I posted.

I installed Chrome Remote Desktop on one of the computes I'm using as a minecraft server and when I run the command given by this web-site //remotedesktop.google.com/headless it gives this output:

--redirect-url="//remotedesktop.google.com/_/oauthredirect" --name=$[hostname] Enter a PIN of at least six digits: Enter the same PIN again: [0915/171037.486929:ERROR:cert_verify_proc_builtin.cc[559]] No net_fetcher for performing AIA chasing. [0915/171038.676267:ERROR:daemon_controller_delegate_linux.cc[101]] Traceback [most recent call last]: File "/opt/google/chrome-remote-desktop/chrome-remote-desktop", line 29, in import psutil ModuleNotFoundError: No module named 'psutil' [0915/171038.676436:ERROR:daemon_controller_delegate_linux.cc[180]] Failed to add user to chrome-remote-desktop group. Couldn't start host.

Article by 2LapsTimeTrial di 7:50:00 PM

If you want to access / remote windows desktop inside archlinux, there are easy way using google chrome remote  desktop. In archlinux you must install chromium browser first, and the windows desktop that you want to remote must have google chrome installed too.

Installation chromium:

$sudo pacman -S chromium

Then open the chromium in archlinux and google chrome in windows, go to chrome store then install "Chrome remote desktop".

Then launch app [Chrome Remote Desktop] both of Windows/archlinux, login with your gmail account.

In windows desktop :

Choose "Share this computer for another user to see and control".

If this apps use for the first time, it will download file, wait until finish and install it. Run chrome remote desktop again,when done, choose "enable remote connections" input your own pin, then choose "Share" until you get code.

Now in archlinux desktop:

Choose access to remote windows desktop, 

and input code that you received from windows desktop.

Then connect:

Now you can access the windows desktop on archlinux :]

If you want to access archlinux in another computer you must install these packages from aur:

//aur.archlinux.org/packages/chrome-remote-desktop/

Then the step is same as above.

That's it enjoy.. :]

Tags : Networking, Remote

I wrote a blog post on getting Chrome Remote Desktop working on Arch [and Ubuntu]. Also included are some modifications to enable mirror mode to share your local desktop instead of launching a virtual session.
If you use VNC, maybe give this a try. Performance-wise it's a big step up.

This probably only works with Xorg. Tested on Gnome, but it might work for other DEs with a little tweaking.

Chrome Remote Desktop has been around for quite a while, but now Google offers a .deb installer with native Linux support via Systemd. This is great because it removes the need to setup VPNs and VNC to remote connect to your machines, or in the case that you need to land a hand to a not so technical savvy family member or friend.

Unfortunately the installer is only for Ubuntu [and Debian based distros], but with a few steps we can get it running on Arch, and [thanks to a patch by nightuser] even configure it to use existing X sessions instead of creating a new one [which is the default behavior].

As expected, the packages exists in the AUR, so the install should be pretty simple.

Instructions

Install

a. Install chrome-remote-desktop from the AUR

b. Run crd --setup to configure your connection. Hit any key

c. Select your Desktop Environment [I selected KDE which is what I use] and save the file

d. Press any key again

e. Enter a new resolution if you would like to use something different than the default [1366x768]. Save the file

f. You should see the confirmation that the setup is complete

g. Go to //remotedesktop.google.com/headless and click on ‘Begin’

h. Click on ‘Next’

i. Click on ‘Authorize’

j. Select the Goole account you would like to use

k. Give it permission

l. Click on the copy the button and paste it on your terminal

m. Give the computer a friendly name and a pin to access it

You should get a confirmation that everything went ok

Starting Xvfb on display :20 X server is active. Launching X session: ['/bin/sh', '/home/victor/.chrome-remote-desktop-session'] Launching host process ['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/victor/.config/chrome-remote-desktop/pulseaudio#ae6329c099/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.victor.ssh_auth_sock', '--signal-parent'] wait[] returned [1092272,0] Host ready to receive connections. Log file: /tmp/chrome_remote_desktop

Additional Configuration

The additional configuration will allow you to connect to an existing session instead of creating a new one when connecting.

a. Find what display number X is using

$ echo $DISPLAY :0

b. Create a file in ~/.config/chrome-remote-desktop/Xsession with the display value

$ echo "0" > ~/.config/chrome-remote-desktop/Xsession

c. Stop the chrome-remote-desktop.service

$ systemctl --user stop chrome-remote-desktop.service

d. Check if it stopped with crd --status. If it did not, stop it with crd --stop

$ crd --status CRD status: STOPPED

e. Take a backup of /opt/google/chrome-remote-desktop/chrome-remote-desktop

f. Download the patched /opt/google/chrome-remote-desktop/chrome-remote-desktop to the same location, or follow the instructions to manually modify your file here.

Note: The patched version was tested with chrome-remote-desktop 81.0.4044.60-1

g. Start the agent with crd --start so you can see verbose output. You should receive a confirmation when it starts

$ crd --start Launching X server and X session. Using existing Xorg session: 0 Launching host process ['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/victor/.config/chrome-remote-desktop/pulseaudio#ae6329c099/fifo_output', '--ssh-auth-sockname=/tmp/chromoting.victor.ssh_auth_sock', '--signal-parent'] Host ready to receive connections. Log file: /tmp/chrome_remote_desktop_20200402_202207_2vtQSb

h. Go to //remotedesktop.google.com/ from another computer and try to access your computer