Just compile and install x11vnc, no need to set up the

Set up x11vnc on your remote computer.

To log into your user, you need an alternative way to access the X server, so that you can enter

That it shows active(running) in green somewhere in the output. You can verify this by running systemctl status rvice and verifying

X server is actually running, but your user has somehow been logged out.

Re-starting the Chrome Remote Desktop Serverīut if the computer shows up as offline with a message ‘X server failed to start or crashed’, that can mean: opt/google/chrome-remote-desktop/chrome-remote-desktop -reload

To solve this, SSH into your remote computer, and reload the server config: Or it might show up as 'Online', but the connection will not go through. It will show up as ‘Offline’ in your local Chrome Remote Desktop screen, with a message ‘Last online on '. If you don’t connect to your remote computer for a few days, you might find that you are no longer able to connect to it. Un-freezing the Chrome Remote Desktop Server After doing this, a nautilus window that you start in one Chrome Remote Desktop session will be there in the next session.įollow the steps mentioned in this StackExchange answer. This is what TeamViewer does, for example. However, if your remote computer has an X session running, it is very useful to keep connecting to that one every time. Reconnect to existing X sessionīy default, it starts a new X session every time you connect to your remote computer. In this post, I want to write about two ways you can hack Chrome Remote Desktop to make it more productive for Linux.įirst, you will of course need to get Google Chrome and set up Chrome Remote Desktop. Its competitor TeamViewer often flags academic use wrongly as commercial use, causing inconvenience. I have found Chrome Remote Desktop to be very useful. Working remotely is essential in these COVID-19 times.

Chrome remote desktop