If policykit broke the desktop and unprivileged profiles this is a bug with policykit not being set up to honor those unix groups.
I don't see user profiles only with respect to g-s-t. It seems usefull also for admins not using g-s-t. As adduser is supposed to be thesystem wide tool, even the installer creating users during install should benefit from it.
Regarding gst-backend features:
* make the frontends fetch defined defaults (and profiles) through the backend
* if adduser is used, backend parses /etc/adduser.conf for active system defaults
* check if it is a symlink
* parse other available adduser.conf.profiles
* option to choose between those profiles (--conf FILE)
* option to switch default system profile (symlink)
* if adduser is not used backend parses /etc/g-s-t/ for defaults and available profiles
If policykit broke the desktop and unprivileged profiles this is a bug with policykit not being set up to honor those unix groups.
I don't see user profiles only with respect to g-s-t. It seems usefull also for admins not using g-s-t. As adduser is supposed to be thesystem wide tool, even the installer creating users during install should benefit from it.
Regarding gst-backend features:
* make the frontends fetch defined defaults (and profiles) through the backend conf.profiles
* if adduser is used, backend parses /etc/adduser.conf for active system defaults
* check if it is a symlink
* parse other available adduser.
* option to choose between those profiles (--conf FILE)
* option to switch default system profile (symlink)
* if adduser is not used backend parses /etc/g-s-t/ for defaults and available profiles