Download ^HOT^ Remote Chrome Desktop
Sharmaine Kass
Tip: Your desktop environment may not support more than one session at a time. In this case, we recommend that you use different desktop environments for your Chrome Remote Desktop session and your local session, or use the session chooser.
If you use the session chooser, we recommend that you sign out of the desktop environment in Chrome Remote Desktop or your local session before you sign in to the same desktop environment on the other.
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
Hi guys, I've been using chrome remote desktop for a while and one day discovered a "magical" behavior. I've left my remote PC asleep and when I tried to connect remotely it just woke my remote PC and connected properly. I've been used to leave my PC asleep for a month or so, but lately it stopped working like that, now I have to leave my PC awake to be able to connect remotely. Can anyone explain how did it happen, and how can I get the feature back. I red on the internet that motherboards have an option called "Wake on LAN", I've enabled that option, but have had no success.
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.
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)
df19127ead