illwieckz
commented
10 months ago The known workaround to use pkexec instead of sudo is to do what the cpufreq GNOME Shell extension does:
- ship with the extension a pkexec policy file
- make the extension check if the pkexec policy file is installed
- if the pkexec policy file is not installed, run pkexec to install the policy file (the extension will trigger a prompt for the admin password)
Actually the cpufreq extension is doing even worse than that because they have more needs and they have to install a script, actually installing and running as root a script that was downloaded from the internet with the extension. LOL.
pkexecis not a replacement forsudoAs far as I know, there is no
pkexecequivalent tosudo --non-interactive.What does
sudo --non-interactive <program>is that if the user has allow the program to be run with sudo, the program is run, but if the user has not allowed program to be run with sudo, the program is not run. People who don't gave permission for the said program will not get the sensor values, people who gave permission for the said program will get the sensor values.With
pkexec, the admin password is asked every second forever, taking priority over every application and making very hard to open the extension preferences to disable the option.Not providing the admin password immediately asks for the password again and forever, providing the admin password immediately asks for the password again and forever.
I know GNOME people asked you to replace sudo with pkexec as you said in:
But well, pkexec cannot replace sudo, as already stated in:
Actually the people asking you to replace sudo with pkexec don't know what they talk about. We have a nail and a hammer and they ask you to replace the hammer with a screwdriver. That doesn't work.