This article describes some differences for Linux users. See this article for a description of the differences between Chromium and Chrome. See Puppeteer.launch() for more information. You can also use Puppeteer with Firefox Nightly (experimental support). const puppeteer = require ( 'puppeteer' ) Ĭonst browser = await puppeteer. You create an instance of Browser, open pages, and then manipulate them with Puppeteer's API.Įxample: navigating to and saving a screenshot as example.png: Puppeteer will be familiar to people using other browser testing frameworks. All examples below use async/await which is only supported in Node v7.6.0 or greater. Starting from v3.0.0 Puppeteer starts to rely on Node 10.18.1+.
Now I can keep the steps straight for the next time I might have to do this again.Prior to v1.18.1, Puppeteer required at least Node v6.4.0. I was successfully able to remotely access the active desktop. Next, I launched Chrome Remote Desktop and noticed that the “Enable remote connections” button was enabled, so I clicked it and entered in a PIN number.Īfter remote connections were enabled, this computer came “online” and appeared online in the list on a remote client computer.
opt/google/chrome-remote-desktop/chrome-remote-desktop -start Final Launch 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:ĭef launch_session(self, x_args): self._init_child_env() self._setup_pulseaudio() self._setup_gnubby() #self._launch_x_server(x_args) #self._launch_x_session() display = self.get_unused_display_number() self.child_env = ":%d" % display Reuse the existing X session instead of launching a new one. #while os.path.exists(X_LOCK_FILE_TEMPLATE % display): # display += 1 On Ubuntu 17.10 and lower, this is usually 0, and on Ubuntu 18.04, this is usually 1:Ĭomment out sections that look for additional displays: Set the X display number to the current display number (obtain it with echo $DISPLAY from any terminal). In my case, I set it to “1920x1200,3840x2400” since the desktop had dual-monitors. Sudo gedit /opt/google/chrome-remote-desktop/chrome-remote-desktopįind DEFAULT_SIZES and amend to the remote desktop resolution. Sudo cp /opt/google/chrome-remote-desktop/chrome-remote-desktop /opt/google/chrome-remote-desktop/chrome-remote-desktop.origĮdit the config file ( sudo vim, gksudo gedit, etc): It is OK if it says that the daemon was not currently running. opt/google/chrome-remote-desktop/chrome-remote-desktop -stop I’m writing the pertinent steps below which were still applicable in 18.04 and the version of Chrome Remote Desktop available as of the writing of this article. Next, I followed this Stack Overflow superuser post from MDMower. I clicked “Launch App” and at this point I’m looking at this:Īdding user to the chrome-remote-desktop group Monkey Patching Chrome Remote Desktop I visited the Chrome Remote Desktop Web Store page and installed it by clicking “Add to Chrome”.
#Linux open google chrome remote install#
Next, I launched Chrome and signed in so that I’d be able to install Chrome apps.
wget sudo dpkg -i google-chrome-stable_current_b
I have never had much success running Chrome Remote Desktop with Chromium. Once that was done, the first thing I did was to install Google Chrome, not Chromium, but Chrome. To begin, I started with a fresh install of Ubuntu 18.04 Desktop. So I decided to try to nail down a concrete set of working steps for myself once and for all. Over the years, I keep trying to install Chrome Remote Desktop but end up dredging up a hodge-podge of articles and forum posts that sometimes lead to dead ends. With Ubuntu 18.04 recently released, I wanted to install Chrome Remote Desktop on it to remotely access my desktop.
#Linux open google chrome remote how to#
How to Install Chrome Remote Desktop on Ubuntu 18.04