If that is a bad thing then try to hold off till you have some safe down time. So basically to keep it simple if the worst case scenario of being unable to use your computer till someone can tend to it is not that bad of a thing to you, go ahead, a remote desktop connection does not put the computer at higher risk of something bad happening. If the update were to fail for some reason and the computer is unable to boot/log in you will be out of contact with it till someone can see what the issue is and fix anywhere from needing to type in a password to worst being go through a Time Machine restore of before the update. However why I recommend against you doing any restarts let alone an update is you are unable to control your computer from the moment you log off to the moment you log back on. Enable the chrome remote curtain mode, which means whenever the host is remotely connected, it always shows blank in host's monitor, and you should lock the host machine after you are done. Switch off the monitor in host machine (semi-secure) 2. I ran: sudo apt-get purge chrome-remote-desktop and then reboot. Yes, just go to on a device that you don't mind signing into with your Google account, and it will walk you through setting up access to the remote machine. To workaround on this for security purposes on host machine, you may: 1. To solve it I pressed Ctrl + Alt + F4 to log into tty4. An hour before I have installed the chrome-remote-desktop. First I would hope that you have a backup of your computer since it sounds like it's important (aka more than just a web browser to you) whether or not you decide to proceed with this update. 1 Answer Sorted by: 2 Eventually this has nothing to do with the way the machine was shutdown. I personally would recommend staying away from anything that requires a restart of a remote computer you don't have easy access to.
0 Comments
Leave a Reply. |