On 2018-05-04 03:09, Patola wrote:
> Adding to a sudo-enabled group is not enough?
No. Authentication happens through PolicyKit, and PolicyKit does not
know about "procer3d".
$ cat /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin
As you can see it does know about the unix group "sudo", and accounts of
the type "Administrator" belong to "sudo". So one way is to do as Jeremy
suggested and change those users accounts to be "Administrator".
Another way is to tell PolicyKit what you want. You can do so by
creating the file /etc/polkit-1/localauthority.conf.d/52-my-admin.conf
and giving it this contents:
[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:procer3d
You can read more about it in "man pklocalauthority".
HTH
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1768995
Title:
The "Unlock" button of user administration asks for wrong user
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
