Download Chrome Remote Desktop Apk
Christia Satchwell
Howerver, starting a remote desktiop session only result with a blank screen. I have tried searching for a solution, but none of them are up-to-date, or gives a helpful hint for a solution. I also tried gnome-session-classic, but without luck, too.
This answer originates from Rob Calistri's comment in François Beaufort's G+ post. Due credit to the source. If you've updated Ubuntu (or Ubuntu Gnome) recently, instead of a blank screen, you likely see just wallpaper without any panels when connecting via Chrome Remote Desktop. This modification forces Chrome Remote Desktop to use the existing X Server instead of creating new desktops.
The chrome-remote-desktop application works just fine with linux generally and Ubuntu specifically. It however does NOT play nice with LightDM and Unity. Ubuntu Bug #1274013, and the related bug in comment #3 shed some light on this: gnome-session is broken without 3d acceleration.
I've only ever used it for that use case - to connect to OSX / Windows boxes from my Ubuntu work laptop. In those instances, the viewer is just accessed by installing via the chrome extension located here: -remote-desktop/gbchcmhmhahfdphkhkmpfmihenigjmpp?hl=en
EDIT: Since the remote-desktop host feature is currently in beta, it's not accessible in the chrome-stable installation, which is why I've not seen it listed and there is no option to enable remote connections in the stable installation, as far as I can tell.
Create a file called .chrome-remote-desktop-session in your home directory. This should be a shell script that starts your preferred desktop environment. Find the correct command to start the desktop by looking in /usr/share/xsessions/ for the desktop entry.
Concretely, let's say you want to map your local (Windows) Ctrl key to the remote (Mac) Cmd key. From the table above we see that the code for the (left) Ctrl key is "ControlLeft", while the code for the Cmd key is "MetaLeft", so from the "Configure Key Mappings" dialog:
At this point you should be able to use Ctrl-C, Ctrl-V etc. on your local PC to trigger the corresponding Cmd-C, Cmd-V etc. commands in the remote Mac. The solution works quite well for me and it resolves a perennial problem of how to use the Cmd button while on a Windows PC without having to rely on external apps or plugins.
I have confirmed, using chrome remote desktop, that search+another_key does the same as CMD+another_key while remote-connected to my mac-book pro over home WiFi. I also noted that if I want to enter two search+another_key presses sequentially, I must release and repress the search key after each instance
Since you want to remotely connect outside your network using Chrome Remote Desktop, then it seems that there is no need to configure LAN WAN Inbound Rules. However, you might need it if ever there will come a time that you want to remotely connect to your network from outside using Chrome Remote Desktop.
I'm trying to use Chrome Remote Desktop to access my machine from a Mac. When I try the "enable remote connections" step it tries for a while then times out with error "failed to start remote access service." If I close the window, then my machine shows up and says "(last online 3:49:58 PM)" where the time is the time I attempted to start the service.
I've tried reinstalling chrome and chrome remote desktop and following the instructions in this question. I can connect to my computer through the "remote assistance," and I can connect to my Mac from my linux machine. Any other ideas?
I think I figured out what was going on. First I deleted my chrome remote desktop installation and all config files associated with google chrome. Then I reinstalled, and followed these edits here so I could remote in to the current session. It worked for about 24 hours, then it failed to connect after that.
The Chromium-browser and Chrome are probably different browsers. Probably, Google cannot give some tokens to the Chromium. Because of the reason, you can carry on the following steps for using chrome-remote-desktop on ubuntu.After this installation, two chrome application is available on your computer. The real one is red-green-yellow colored.
I have a server running Ubuntu Server 16.04, started from stock installation with SSH server. Currently, I have full access to the machine with public key SSH access. Since the machine is running non-critical resources, but I don't have easy physical access to it, I would like a non-SSH method of remote access that doesn't rely on functional upstream port-forwarding or the safety of my local machine(s) with private keys that can access the server. This would enable me to continue to manage the system and verify that it is still operational. The most evident end-to-end solution would be to use Chrome Remote Desktop. However, this seems like it would be a bit of a challenge to get setup.
Note that my desired access requirements preclude the use of VNC or other, more typical remote access programs. The fact that Chrome Remote Desktop 'calls home' to start connections, mediated by Google, is the feature I'm most after. I may consider alternative services in the comments, but please keep answers to the Chrome Remote Desktop method.
I'm trying to setting up Chrome Remote Desktop on my VM instance (Debian GNU/Linux, 9 (stretch), amd64) on Google cloud. I tried to install Xfce as desktop environment. I installed Xfce component successfully with these command.
This tutorial shows you how to set up theChrome Remote Desktop service on a Debian Linux virtual machine (VM) instance onCompute Engine. For separate instructions for Windows VMs, seeWindows virtual machines.Chrome Remote Desktop lets you to remotely access applications with agraphical user interface from a local computer or mobile device.
You can use other desktop environments, but Chrome Remote Desktop does notsupport 3D graphics acceleration. If you do choose a desktop environment thatuses 3D graphics acceleration, you need to disable that feature, or the remotedesktop service won't start.
If you installed the Xfce desktop, the first time you connect, you are promptedto set up the desktop panels. Click Use Default Config to get the standardtaskbar at the top and the quick launch panel at the bottom.
The Cinnamon desktop uses several graphical features and animations, such assemi-transparent windows and menus that fade in and out. Because theseanimations take more time to render over a remote connection, it can make theuser interface feel slow.
The user account created by Compute Engine doesn't have a password.However, several desktop environments require one for unlocking screensaversand authorizing administrative actions. It is therefore important to set apassword for your user:
In the preceding section, you set a default desktop environment in the global/etc/chrome-remote-desktop-session configuration file. You can also choose adifferent desktop environment (if it's installed) by specifying it in the.chrome-remote-desktop-session configuration file in your home directory:
As mentioned before, Chrome Remote Desktop does not support 3D graphicsacceleration. Therefore, for any desktop environments that uses these features,you need disable 3D graphics, or the session will not start.
If you have mistakenly disabled connections to the remote instance in theclient app, you can reconfigure the service and re-enable it by following theinstructions inConfiguring and starting the Chrome Remote Desktop service.
Check the contents of the global/etc/chrome-remote-desktop-session configuration file and theuser-specific /.chrome-remote-desktop-session configuration file and confirmthat the specified desktop environments are installed.
3. Here comes the problem. I tried to go to the root in the remote desktop, but VM asked for a password. I have no idea what this password comes from, and I tried the instance id and my gmail password, not working. (figure shows the remote desktop)
This is a big problem for me since I want to control my p1s from a chromebook sitting next to the p1s. Is there any way for me to fix this on my end? I doubt bambu labs will change something this fundamental.
Chrome Remote Desktop is a remote desktop software tool, developed by Google, that allows a user to remotely control another computer's desktop through a proprietary protocol also developed by Google, internally called Chromoting.[2][3] The protocol transmits the keyboard and mouse events from the client to the server, relaying the graphical screen updates back in the other direction over a computer network. This feature, therefore, consists of a server component for the host computer, and a client component on the computer accessing the remote server. Chrome Remote Desktop uses a unique protocol, as opposed to using the common Remote Desktop Protocol (developed by Microsoft[4]).
The Chrome Remote Desktop client was originally a Chrome extension from the Chrome Web Store requiring Google Chrome; the extension is deprecated, and a web portal is available at remotedesktop.google.com. The browser must support WebRTC and other unspecified "modern web platform features".[5] The client software is also available on Android[6] and iOS.[7]
If the computer hosts remote access, such as for remote support and system administration,[8] a server package is downloaded.[9] A Chromium-based browser that supports Chromium extensions such as Google Chrome or Microsoft Edge must be used. This is available for Microsoft Windows, OS X, Linux and ChromeOS.[10]
The Chrome Remote Desktop allows a permanent, pre-authorized connection to a remote computer, designed to allow a user to connect to another one of their own machines remotely.[11] In contrast, Remote Assistance is designed for short-lived remote connections, and requires an operator on the remote computer to participate in authentication, as remote assistance login is via PIN passwords generated by the remote host's human operator. This method of connection will also periodically block out the control from the connecting user, requiring the person on the host machine to click a button to "Continue sharing" with the connected client.[citation needed]
f448fe82f3