![]() In terminal, it seems I'm logged in as my usual user. For example trying to enable my OpenVPN connection returns: If I try and do anything important (e.g restart, change networks, install software) through the GUI I get a permissions error. When I log in directly to the box, all is fine - the problem appears when I connect using Chrome Remote Desktop. Back in 2015, ChromeRDP was as simple as one-click install on Linux and it never gave me a single issue.I'm connecting to my remote server running Xubuntu. Unfortunately, you missed the easiest RDP software that ever existed by about 6 years. ![]() I wish I could be more help and I realize that this is not much of an answer, but I hope that explaining my struggles and how ChromeRDP finally broke completely (every successive update to date has made ChromeRDP more and more buggy on Linux) might help. To date, I have yet to find any other suitable no-port-forwarding alternative RDP software. it's a laptop), then (as far as I can tell) you're SOL. So, the solution is to just port forward. Anyway, I had countless issues with ChromeRDP prior to it breaking completely, including random disconnects, broken x sessions, freezing up the x session, black unusable desktop, randomly stopping working, the computer suddenly disappearing from the list of connectable computers, etc. Then, I gave up on ChromeRDP because it appears there is no solution to the problem (at least none I could devise). ![]() I'm running a server, so I can't open x to all local users, so I tried for an hour to find a fix to no avail. I patched it to make it connect to the existing physical screen, which worked previously (before the update), but it doesn't work now due to (what appears to be) xauthority issues. ![]() And finally, I have stumbled at the step usermod -a -G chrome-remote-desktop "$USER" of the mentioned thread Can't Configure Chrome Remote Desktop for it returns usermod: group 'chrome-remote-desktop' does not exist and I do not understand whether it is important (but it looks like logging does not work without this step).įor me, Chrome Remote Desktop recently updated and I was unable to start a xsession due to errors. Unfortunately, it has been just a part of the problem, CRD still fails to run. It helped me to actually start the service. So, I followed the second answer (again, not the accepted one) of. not running.Įxecuting sudo systemctl unmask rvice changed nothing. I executed service chrome-remote-desktop status and realised the CRD service was masked, i. I found an informative answer on how to start investigating the issue in the thread Can't Configure Chrome Remote Desktop (it is not the accepted answer, but the second one). Did not change a thing.Īlso, I tried to uninstall it with dpkg -purge. I found this advice: How can I "Turn On" Chrome remote desktop in Ubuntu 20.04?. ![]() exactly the same deb-file (this time with GUI tools: Qapt or Discover). Should I click the blue button it initiates downloading and installing. Then I launched it only to get this screen: After adding a couple of required dependencies it has set up smoothly. I need to be able to connect to computer running Lubuntu 20.04 with Chrome remote desktop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |