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. 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. 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). Ubuntu supports multiple display sessions, and Chrome Remote Desktop will (by default) leverage this feature. MONKEY GUIDE FOR SHARED SESSION IN CHROME REMOTE DESKTOP Do this before reboot to avoid a boot loop. Important: follow the monkey guide below to share the same session instead of starting another #. If it stays on the final setting up stage for more than thirty seconds, try reloading the page - it might have taken effect. Go to the Chrome Remote Desktop site in Chrome and the machine should be configurable now (press "Turn On" and follow the prompts).Ĭonfigure computer name and PIN. Populate the servier IP and make a config and save it (might be able to edit the sktop file to autopopulate this by changing: Step 3aīARRIER CLIENT - ĭownload the snap from ubuntu software center ![]() 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. This has some security implications so read the warning that pops up carefully. Right click on that folder, and choose Change Password enter your old password, and make your new password blank. ![]() 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. ![]() It really shouldn't matter, but correcting the case (to lower case) might save you a re-install down the line.Īfter you've installed Chrome, you might get a keyring popup every time you reboot. For some reason, the installer will set AutomaticLoginEnabled to True instead of true (note capital T). If you enabled automatic login during install, you might be able to recover things at this point. This will let you use "sudo atom -no-sandbox " to edit locked files. INSTALL ATOM - ĭo not use the snap from the software center as it will not allow you to edit files with sudo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |