Comment 12 for bug 1008344

@Gunnar: As I said in the bug report, this is an installation which uses user accounts and groups from an LDAP directory. There is an LDAP group for all network-wide admins, and I am in this group. This group is enabled for sudo and policykit admin rights in the appropriate config files, and I expect all users within this group to have all available permissions. I certainly don't want to edit code files in /usr/lib to give myself additional rights.

I also don't want do put all admin users into the local groups "sudo" or "admin", because this defeats the whole purpose of an LDAP directory (i.e., I would have to change files on all machines in the network whenever there is a new admin or one leaves). It is also not an option to distribute the groups "sudo" and "admin" via LDAP, because then nothing works on the machine in an emergency when the LDAP server is down (it is generally not recommended to distribute any uids and gids < 1000 via LDAP for this reason).

You are also wrong about the "way that is compatible with how Ubuntu handles these things". Ubuntu uses sudo and policykit, and I am using these ways.

Note that language-selector does not need to know about the existence of any files (and should not), it should just ask policykit whether the user has admin rights. That's the way all other applications work (if they don't use sudo).