10-14-2018, 03:22 PM
I recently installed Linux Lite 4.0 (release 18.04) on an older PC with a plan to run the PC headless and access it over my local home network via a VNC connection.
So I installed vnc4server and was able to successfully connect to it using a TigerVNC client on a Windows10 PC. However, as I started doing things over the VNC connection, I noticed that programs requiring admin rights did not work.
For example, the File Manager works just fine until I try to do an "Open as Administrator". When I do try that, nothing happens when I use the VNC connection. However, this works just fine when I use a monitor and keyword connected directly to the PC.
This issue also exists with other things like System Install/Remove Software and Settings Firewall Configuration. For all of these, I never see the Authenticate popup window to enter a password when connected via VNC.
Finally, I have experimented using x11vnc on this PC and I do not see the same issue when accessing the PC over that VNC connection. I assume that is because x11vnc is sharing the existing X session rather than opening a separate session like other VNC servers.
Any comments/suggestions/alternatives to resolve this admin rights issue would be greatly appreciated.
Thanks in advance, Paul
So I installed vnc4server and was able to successfully connect to it using a TigerVNC client on a Windows10 PC. However, as I started doing things over the VNC connection, I noticed that programs requiring admin rights did not work.
For example, the File Manager works just fine until I try to do an "Open as Administrator". When I do try that, nothing happens when I use the VNC connection. However, this works just fine when I use a monitor and keyword connected directly to the PC.
This issue also exists with other things like System Install/Remove Software and Settings Firewall Configuration. For all of these, I never see the Authenticate popup window to enter a password when connected via VNC.
Finally, I have experimented using x11vnc on this PC and I do not see the same issue when accessing the PC over that VNC connection. I assume that is because x11vnc is sharing the existing X session rather than opening a separate session like other VNC servers.
Any comments/suggestions/alternatives to resolve this admin rights issue would be greatly appreciated.
Thanks in advance, Paul