Google chrome remote desktop linux

Chrome Remote Desktop Install for Linux

Chrome Remote Desktop Install for Linux

Here I will explain how to install and setup Chrome Remote Desktop install for Linux.

You will also see how to Enable remote connections on your Linux box so you can log in unattended, 24/7.

**** NOTE: make sure you have a backup. I am still working on the .chrome-remote-desktop-session file. right now is messing up the desktop. So only set this up right now if you have a very good back up of your Box…. Just warning you….***********

Set up Chrome Remote Desktop

Step 1:

Install the Chrome Remote Desktop app on every computer you want to access remotely and every computer you’d like to connect from.

1. Visit the Chrome Remote Desktop app page in the Chrome Web Store.
2. In the upper-right corner of the window, click the blue + Free button to download Chrome Remote Desktop.
3. Click Add in the confirmation dialog.Once the app has been added, the Chrome Remote Desktop icon will appear in the App Launcher When you open Chrome Remote Desktop app for the first time, you’ll be asked to authorize it. This will allow the app to do the following:

• See your email address
• See your Chrome Remote Desktop computers
• Receive and send chat messages (this is how we get the two computers to “talk” to each other)

Stop here and go to the next section Install the Debian package

Applies only Debian and Ubuntu – Mint (12.04 or higher)

Chrome Remote Desktop for Linux is currently in active development. To run this app on Linux, you’ll need to create a separate virtual desktop
session.

Install the Debian package

Download and install one of the following Debian packages for the Host components. When you click one of the links below, the package will
download automatically. Click on the package you need and download it.

The software will update on its own.

Now open a Terminal Window and change to your Download directory by typing in Exp: cd /home/bob/Downloads and hit enter

Now in the Terminal Window type in sudo dpkg -i chrome-remote-desktop_current_amd64.deb then hit enter (or sudo dpkg -i chrome-remote-desktop_current_i386.deb if you have a 32 bit box)

Next type in: sudo /etc/init.d/chrome-remote-desktop stop then hit enter This makes sure the service is not running yet….

Step 2:

Create a virtual desktop session

1. Create a file called .chrome-remote-desktop-session in your home directory. This should be a shell script that starts your preferred desktop environment.
2. Find the correct command to start the desktop by looking in /usr/share/xsessions/ for the desktop entry. For example, has the line: (This was for a Mint 17 XFCE box) Open a simple Text Editor and add just the following line. Then save the file to your Home Directory. Exp: save to /home/bob/ .chrome-remote-desktop-session
   startxfce4

3. Now with the Text Editor already open, find the file .profile from your home directory Exp : /home/bob/ .profile (Note: any file that has a .
(period) in front of it is a hidden file.

4. At the end of the file on a new line add the following

Now Save the file…

5. Next type in your Terminal Window: sudo /etc/init.d/chrome-remote-desktop start then hit enter

Making it all Work…

Enable remote connections

1. Open the Chrome Remote Desktop web app.
2. Click “Enable remote connections.”
3. Enter a PIN and re-type the PIN. Then click OK.
4. Dismiss the confirmation dialog.
5. Close all programs and then reboot

That should be it, you should be able to log into the box you just set up with Chrome Remote Desktop. Just don’t forget the pin you created. If you forget you can always go back into Chrome and disable and then re enable Enable remote connections it will ask you for a new pin number.

Reference for this article can be seen at: Chrome Remote Desktop

Источник

Install and Setup Chrome Remote Desktop on Ubuntu 18.04

In this guide, we are going to learn how to install and setup Chrome Remote Desktop on Ubuntu 18.04. Google has developed a remote desktop tool called Chrome Remote Desktop that allows users to remotely access and control another computer over the Internet through a protocol called Chromoting on Google Chrome browsers.

Install and Setup Chrome Remote Desktop on Ubuntu 18.04

To setup Ubuntu 18.04 to be accessed via Chrome Remote Desktop, follow the following steps.

Sign in to your Google account

Before you can proceed, fire up your Chrome browser and navigate to Google login page and sign in to your Google Account using your gmail account.

Install Chrome Remote Desktop Extension

Once you are logged in to your Google account, proceed to install the Chrome Remote Desktop Extension on your Chrome browser.

To install the extension, navigate to Chrome Remote Desktop extension page and click add to Chrome. When clicked, a confirmation Window pops up. Click Add Extension to install the Chrome Remote Desktop extension on your browser.

Install Chrome Remote Desktop Package

When you add the Chrome Remote Desktop extension, download chrome remote desktop package which provides the required host components and install it as follows.

Chrome remote desktop installs as a service, chrome-remote-desktop.service and is set to run upon installation. It is also enabled to run system boot.

It also creates a group called, chrome-remote-desktop.

Allow Remote Desktop Connections

To allow remote computers to connect to your desktop, click on the Chrome Remote Desktop extension on the extensions bar or simply enter the address https://remotedesktop.google.com/access.

Click TURN ON to enable remote desktop access.

Next, set the system name.

Set the remote desktop connection PIN. This is the authentication PIN that the remote user will need to use to access your remote desktop.

Click Start to start Chrome remote desktop daemon. If you had logged in as non root user, you are prompted to authenticate in order to run chrome-remote-desktop service as superuser. At the sametime, the same user is added to chrome-remote-desktop group.

When the setup is done, your remote desktop goes online and you can now be able to access it remotely.

Accessing Ubuntu 18.04 through Chrome Remote Desktop

Now that the Chrome remote desktop is setup on your Ubuntu 18.04, if you need to access it remotely, you have to sign in to Google account using the same email that is used to on the remote system.

Once you sign in to your Google account, install the Chrome Remote Desktop extension and the Chrome Remote desktop Debian package as described above.

Once that is done, open the Chrome Remote desktop extension from the same Google account as on the remote system and you should be able to see your remote system online.

Click on the name of the remote system to start a remote session. You will be prompted to enter the remote desktop authentication password set above.

Click enter to authenticate to remote desktop.

You should now land on the remote desktop system user authentication screen. Login to access your system.

Upon successful authentication, you should get to your Ubuntu 18.04 remove desktop.

You have successfully connected to a remote desktop computer using Google chrome remote desktop.

And that brings to the end of our guide on how to install and setup Chrome Remote Desktop on Ubuntu 18.04. Enjoy

RELATED ARTICLESMORE FROM AUTHOR

Quick Way to Install LEMP Stack on Debian 11

How To Safely Download And Watch Movies

Install and Setup OpenLDAP Server on Debian 11

Install ClamAV on Debian 11

Do You Own An Online Business? Here’s How To Monitor Your Employees

Install Guacamole on Debian 11

9 COMMENTS

Thank you for writing this article.

I thought I would leave a comment on my experience as I attempted this from a Linux install on VMWare. The VMWare instance works perfectly and I went to install chrome remote desktop as in the article. The install was successful, no errors, warnings or issues.

However, I can’t get the remote desktop to come online from the browser. From the chrome browser I navigate to “remotedesktop.google.com” and choose my Linux environment from the list, and enter in the PIN. I am then presented a dialog with the instructions and following two choices (difficult to illustrate without a screenshot, hopefully you can see what I’m trying to show):
=-=-=-=-=-=-=-=-=
Select a session to launch within your Chrome Remote Desktop environment. (Note that some session types may not support running within Chrome Remote Desktop and on the local console simultaneously.)

Name Comment
(X) (default) Launch the default XSession
Ubuntu This session logs you into Ubuntu

Neither of the choices work. They both present a black screen which terminates after a couple min. I haven’t spent any time looking into it, just thought I would post some feedback.

Hello matt. Thank you for feedback. You can upload screenshot via google drive and share the link.
However, if you fix the issue, we will appreciate the feedback too.

I’m getting the same issue. Below is the link:
https://drive.google.com/open?id=1Mgkfuol3hGmwLBw23zbvzZcoSt6-vHa1
I’ll try to fix it, if I do get through then will post the steps as well.

Sorry but i cant reproduce the error. Please, we will appreciate if you share fix when you find one.

any advice for getting this running with CentOS/Fedora? I tried using Alien to convert the .deb installer to a .rpm but no luck :/

Hello Dan, seems this is not supported out of the box at the moment. If we ever find a hack, we will be happy to post.

i met the same issue with you, have you fixed it?

This worked for me:

After a reboot, once you are logged in and you connect via Remote Desktop it will mirror the current session on your desktop remotely.

When I get to the step “Setup Remote Access”, I get the prompt to “Accept and Install” which downloads the .deb package and installs it, but it never launches and then Setup Remote Access message eventually changes to “This is taking longer than expected.” Once it’s installed, is there a way to force the prompt to appear so I can continue?

Источник

Google chrome remote desktop linux

How to get Barrier and Chrome Remote Desktop working in Ubuntu 20.04 (Focal Fossa)

This is a step-by-step guide to get Ubuntu up and running with a few helpful aplications/configuration/fixes:

Automatic login Atom — a great GUI text editor Barrier — a great KVM program (like Synergy, but free!). Lets you copy and paste between machines. Chrome Remote Desktop — my RDP of choice because the phone app is great for remote admin. Fix for checkdisk operation on boot with some M.2 drives. Change from wayland to x11 for chrome remote desktop — part of a preventative measure against a login loop error Chrome browser

This guide is structured in such a way that you can choose some or all of these changes at your discretion. These just happen to be the programs I enjoy using and I know they are not best practice/most secure, I’m sure someone smarter than myself could automate this via chef/ansible or something.

None of this work is my own, but it took far too many hours of troubleshooting/google-fu to figure out how to get this to run so I figure I would save someone else the headache.

The expected result for my setup was as follows:

• windows machine = MAIN
• Ubuntu machine = UBUNTU
• monitor 1 = MON1
• monitor 2 = MON2

• MAIN on MON1
• UBUNTU on MON2
• share single mouse/keyboard on MAIN with UBUNTU via barrier, mouse can go from MON1 to MON2 for local control
• control UBUNTU on same session shown on MON2 remotely via chrome remote desktop
• UBUNTU logs in after reboot/power restore starting both barrier and chrome remote desktop

INSTALL ATOM — [optional — replace commands in this guide containing «atom —no-sandbox» with you alternative]

Do not use the snap from the software center as it will not allow you to edit files with sudo. This will let you use «sudo atom —no-sandbox [/dir/to/file/somefile.extention]» to edit locked files. Less secure, but less of a headache IMO.

Follow the official guide located at:

As an alternative, you can use pico (a command-line editor which Ubuntu ships with) by running

During the initial Ubuntu installation, DO NOT choose the auto login option. You’ll have automatic login working at the end of this guide, but it’s important you start with manual login to avoid a login loop error.

In the autologin conf file

uncomment the line

You’ll also need to specify the user by uncommenting the next line and adding your username;

If you enabled automatic login during install, you might be able to recover things at this point. For some reason, the installer will set AutomaticLoginEnabled to True instead of true (note capital T). It really shouldn’t matter, but correcting the case (to lower case) might save you a re-install down the line.

After you’ve installed Chrome, you might get a keyring popup every time you reboot. If this happens, launch Passwords and Keys from the app menu; you might need to hit the «back» arrow in the upper left, but you’re looking for a screen that reads «Passwords and Keys» with a «Login» folder. Right click on that folder, and choose Change Password; enter your old password, and make your new password blank. This has some security implications so read the warning that pops up carefully. The password manager might crash on your next reboot, but this will be a one off — on subsequent reboots you should be into Ubuntu smoothly with no extra passwords / clicking around required.

BARRIER CLIENT — [optional — used as a KVM for sharing a single mouse & keyboard so you can display your machine on a second monitor]

download the snap from ubuntu software center [see BARRIER ALT below for terminal install steps for automation]

populate the servier IP and make a config and save it (might be able to edit the barrier.desktop file to autopopulate this by changing:

create a Startup application

check that the .desktop file is in the

add barrier to the favorites close it then reopen from favorites bar. Client should be checked, server ip grey with the ip populated, auto-config checked.

BARRIER CLIENT ALT

• install barrier from terminal (for automation in future)

Open up a terminal window

Issue the command

CHECKDISK ON BOOT ISSUE (Might not be an issue — skip this if you’re not seeing errors)

add parameter fsck.mode=skip before quiet splash then save

You should have done this earlier during auto login setup, but double check Wayland is disabled:

This line should be uncommented:

Restart gnome so it takes effect.

Download the .deb file (or follow Google’s instructions)

install the file

Start Chrome, log in to your Google account.

CHROME REMOTE DESKTOP

Download the .deb for the client:

Make the config directory:

Stop and start the service:

Go to the Chrome Remote Desktop site in Chrome and the machine should be configurable now (press «Turn On» and follow the prompts).

Configure computer name and PIN. If it stays on the final setting up stage for more than thirty seconds, try reloading the page — it might have taken effect.

Important: follow the monkey guide below to share the same session instead of starting another #. Do this before reboot to avoid a boot loop.

MONKEY GUIDE FOR SHARED SESSION IN CHROME REMOTE DESKTOP

Ubuntu supports multiple display sessions, and Chrome Remote Desktop will (by default) leverage this feature. That means you can be connected on the machine itself, and have several applications open; when you connect over remote desktop, it will start a new session (without your existing state). Conversely, if you start doing something remotely, then try to finish it up on the machine locally, all the apps you had open won’t appear on the local display. As well as being a bit annoying, this can cause all sorts of nasty bugs (e.g the most recent state in one session clobbering the other during shutdown; launching applications in one session and they actually appear in the other. it’s a real mess). Follow these steps to override the «smart» functionality, and just have a single session that’s shared between local and remote access.

There are probably some very clever reasons to run it the default way, and changing it like this is less secure — for example, if you unlock the machine remotely over RDP, the machine unlocks on the local session too — someone with physical access could see your mouse moving around, watch what you were typing or even take over with a keyboard / mouse. That said, I just can’t get it to work at all in the default setup, so «less secure and working» is good enough for me..

Stop Chrome Remote Desktop (It is OK if it says that the daemon was not currently running)

Backup the original configuration

Edit the config file

Find DEFAULT_SIZES and amend to the remote computer’s resolution. Example:

Find the local display number in Terminal:

Set the X display number to the current display number (that you found in the previous command, mine was :0)

Comment out sections that look for additional displays:

Reuse the existing X session instead of launching a new one. Alter launch_session() by commenting out launch_x_server() and launch_x_session() and instead setting the display environment variable, so that the function definition ultimately looks like the following:

Save and exit the editor.

Start Chrome Remote Desktop:

On a seperate computer, login to the remote desktop. If you have the host machine hooked up to a monitor, you should be seeing that the remote session is controlling what ever’s on the screen of the local monitor.

A note on headless setups

Once you’ve got your computer reliably, remotely accessible, you might be tempted to remove the monitor (especially if it’s a media server or similar that you very rarely use locally). This can cause problems — Linux is smart enough to check if a monitor is connected as it starts up. If there’s nothing there, it won’t output any video or start a display session — which is what you need to connect remotely. The good news is this is a problem for crypto farmers too, so there are lots of little gadgets you can make or buy that plug in to the video port and trick the computer (at a hardware level) into believing there’s a screen attached. This means a display session will spin up at boot time, which you can in turn connect to.

You should do your own research, but my attempts to DIY by shorting pins on a VGA adapter with resistors didn’t trick my motherboard. I ended up buying a headless HDMI Dummy Plug — lots of options on eBay, mine cost about 5 AUD.

PREVENT CHROME REMOTE DESKTOP LOGIN LOOP

Edit the config to add an early exit before initialization; this prevents Chrome Remote Desktop from starting before login:

All you need to do is add an exit after the beginning of the file, should look like this:

Save and exit your editor.

Add Chrome Remote Desktop to startup applications (just search Startup Applications from the app menu and add a new entry). This starts it AFTER the autologin.

Источник