sudo affects realVNC Server Authorization
I have recently upgraded to Fedora 34 from Fedora 24. The one major change that was made was moving to the forced use of 'sudo' instead of my preferred 'su' This has interfered (I think) with my authorizing the setup of 'realVNC Server. Now the realVNC Server seems not to start. When i start vnc server, I get a command window, where I put in the 'root password' of my Fedora 34 system to allow 'realVNC Server' to run as a .service. This attempts to work but fails with the following error: Administrative privileges are required for this operation. (preceeded by a red circle with a white X in it).
Everything works up to the authorization to set the realVNC Server Password. Frustrated ...
Maybe I have to add something to the wheel group or whatever.
Please note that making changes to VNC's scripts may be overwritten following any updates to VNC Server that you install.
As an alternative to Arthur's change, you could edit /etc/vnc/vncelevate and change the PREFER_SUDO line to true, as we currently set this to false on Redhat based platforms.
Hello Robert, I ran into the same problem and I managed to go around it by editing the command associated to xterm within /etc/vnc/vncelevatecfg to look like this:
SU_LAUNCHCMD=xterm -T DESCRIPTION -e sudo su -c COMMAND_SINGLE_ARG
(In short, I replaced su - with sudo su). Then as my user is in the sudoers file, the user password was accepted and thus the command was successful.
i am not clear, can you explain me detail step to config this /etc/vnc/vncelevatecfg ??
Hi Gaspol, I think the script in question may differ with the version of VNC Server you use. Look inside the script for either the command line option I mentioned in my initial response, or, for a comment in the script mentioning Fedora and/or Red Hat. For the later, the default flag option is set to false, so change the value to true and do the sign in process again. Good luck!
Please sign in to leave a comment.