- /etc/PolicyKit/PolicyKit.conf
- /var/lib/polkit-1/localauthority/10-vendor.d/10-live-cd.pkla
- /home/*/.su-to-rootrc
- /home/*/.*/share/config/kdesurc
- /home/*/.*/share/config/tdesurc
(Note: the last three also need to be added to home_boot_exlclude.list)
...and make sure policykit-1-gnome is installed.
Edit: added files specific to kde or tde.
]]>cheers,
]]>The more I try to make things work the more sense Steve Litt's article makes https://sysdfree.wordpress.com/112/
]]>In the upgraded Devuan:
Tried adding policykit-1-gnome first, and now gparted and synaptic don't start. Tried from the menu and from the terminal with pkexec.
However, I can do 'pkexec /usr/sbin/adduser buford' and it works. Had to use the full path with adduser.
]]>I did notice in another installation that lxqt did it right. I guess the lx teams know what they're doing.
]]>pkexec allows primary user to install and remove software (didn't test gparted this time)
It does not allow primary user to create a new user, and it does not let the second user install software.
I will get around to filing a bug report.
]]>Tested another install on the same machine. This one started as a minimal install, upgraded to ascii, then added apps. In xfce and openbox, gparted won't start from the menu, but if I start gparted-pkexec in terminal, it asks for password. This install also has lxqt, and there, I get a graphical window asking for the root password like it should. (lxqt-policykit-agent runs)
I seem to be the only one with this problem (the one in the subject line) so I won't file a bug report on it. At some point I'll do another refracta jessie to ascii upgrade and watch what happens. The current one has been through a lot to get where it is.
]]>Take a look at the thread I just oppened up. http://dev1galaxy.org/viewtopic.php?id=1555
Both I and fsmithred are running LXDE (if I am not mistaken as mentioned in another thread).
I have also installed eudev in all my installations.
My ascii is an evolution from previous edition of miyo linux.
My ceres is from scratch installation from Devuan 1 Live.
All LXDE.
All LXDE for years if you include Debian as "somehow" related distro.
NOT ONCE, have I run gparted without a password, unless one would consider running from the terminal where sudo was used right before and the session didn't expire. But gparted-pkexec is different from sudo gparted-pkexec in when it will ask for the password.So what can explain the difference between my and fsmithred's experience
It's a mystery wrapped in an enigma. Or is it the other way around? :-)
BTW, I am running eudev as well, and everything seems to be nominal.
I will check out your new thread...
]]>Both I and fsmithred are running LXDE (if I am not mistaken as mentioned in another thread).
I have also installed eudev in all my installations.
My ascii is an evolution from previous edition of miyo linux.
My ceres is from scratch installation from Devuan 1 Live.
All LXDE.
All LXDE for years if you include Debian as "somehow" related distro.
NOT ONCE, have I run gparted without a password, unless one would consider running from the terminal where sudo was used right before and the session didn't expire. But gparted-pkexec is different from sudo gparted-pkexec in when it will ask for the password.
So what can explain the difference between my and fsmithred's experience
]]>[Edited to mention that I'm running with MATE.]
]]>Because that will do exactly what you are describing.
]]>Thanks for the reminder. I tried replacing mate-polkit with policykit-1-gnome and I get the same behavior. (gparted runs without password).
I tried running without a display manager, and I'm getting inconsistent results. Sometimes I can break it so gparted doesn't run (in terminal it gives me an error message about trying to run it as another user and I don't have permission) and sometimes it does run. And sometimes I end up with no input in console and have to use sysrq keys to reboot.
So far, I have not found the right combination to cause pkexec to ask me for a password. At least not today. I have been asked for a password in terminal a couple days ago.
]]>