Google Chrome Remote Desktop for Linux beta is ready for testing

Google has released a beta version of Chrome Remote Desktop to Windows, Mac and Android users. Using Chrome Remote Desktop, users can access another computer through Chrome browser or Chromebook. You can follow the guidelines and FAQs in this page to use Chrome Remote Desktop. If you are interested in discussion on this app, head over to Google’s product forums page here.

Source

Here is the content from Naalie R W’s post on Google’s product forums:

We are excited to announce official Linux support in Chrome Remote Desktop with step-by-step directions provided in our Help Center article linked here. You can find instructions under Set up Chrome Remote Desktop > Enable remote access > Linux (Beta).

Take a look below for some helpful tips and basic troubleshooting recommendations from the development team to make the most of your Chrome Remote Desktop experience on Linux!

Setting the resolution of the virtual desktop: By default, the system will create a virtual desktop that is 1600×1200 pixels in size. To change this, add this line to your ~/.profile script:

export CHROME_REMOTE_DESKTOP_DEFAULT_DESKTOP_SIZES=1024×768

If the session is already running, you will need to restart it for this setting to take effect:

sudo /etc/init.d/chrome-remote-desktop stop

sudo /etc/init.d/chrome-remote-desktop start

Having Trouble?

1. Running Chrome in the virtual session

The virtual session is set up so that, when you run Chrome from within the virtual session, it will be set up with a new profile. This is done because Chrome does not support using multiple X displays within the same profile. You can use Chrome Sync to synchronize your bookmarks and other settings within the virtual session.

2. Viewing the host service logs

The virtual desktop is created by the system init.d service “chrome-remote-desktop”. This service is started from the web-app when you enable remote connections. Each time this service runs, it creates a log file named /tmp/chrome_remote_desktop_… (the suffix contains a timestamp and a random string).

If the service fails to start (or only runs for a short while), this might be because the session is not properly configured. If this occurs, take a look at the log file.