After pushing Chrome Remote Desktop to mobile, Google has finally announced official beta Linux support for its remote access and administration product.
Earlier this year, Chrome Remote Desktop support was extended from Windows and OS X to Android, allowing users of the extension to get remote access to their Windows, Mac, and Linux desktops from the Chrome browser.
But while Google promised that iOS support would come later this year, at the time there was no mention of equivalent support for remote access from a Linux machine.
That changed with a recent update to Google's support pages where it has included instructions for how to set up Chrome Remote Desktop support on some Linux distributions. As the page notes, the beta Linux program is limited to Debian and Ubuntu 12.04 or higher.
Unlike the desktop versions for Mac and Windows, there is no Chrome extension for Linux machines on the Chrome Web Store yet, and the app is "currently in active development".
To run the app, users will need to create a separate virtual desktop session. Currently there are a 32-bit and 64-bit Debian package available to install.
Users running Ubuntu 12.10 or higher will need to follow Google's configuration steps to set up a the virtual desktop session while Ubuntu 12.04 will select Unity 2d desktop by default.
One user has managed to get the beta product working under Fedora, however, they reported that there are a few errors. Google has listed a number of trouble-shooting options for users on its product forums.
The arrival of remote desktop support for Chrome on Linux is late but it merely adds another way for Linux users to remotely access devices over the internet.
Chrome Remote Desktop requires users to have a Google Account and Google also recommends adding a six-digit PIN to the app in the event that someone hijacks the account. It allows a remote connection with the same Google Account, so long as the device is on and connected to the internet. To handle remote connections with other account owners, users can share access via unique access codes that are generated for each session.