GNOME Bugzilla – Bug 466183
Gconf tweak to show all users / groups on system in Users and Groups tool has no effect
Last modified: 2007-10-05 13:25:22 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/124993 "Binary package hint: gnome-system-tools Even using the hidden gconf tweak to show all the users on the system (really, this should be part of the tool - with the appropriate warning that these are system accounts and should not be modified unless necessary - see system-config-users as an example), some users and groups are not shown in this tool - eg, the disk group. The gconf tweak in fails to do what it is documented to do in its description. Can be reproduced by; Opening gconf-editor, visiting /apps/gnome-system-tools/users and enabling showall. Clicking System -> Administration -> Users and Groups. Looking for an a group called disk. Compare with results of 'getent group disk' on command line. ..."
Fixed in svn trunk! 2007-09-06 Carlos Garnacho <carlosg@gnome.org> * users-tool.c (gst_users_tool_constructor): Added, get gconf values there, after tool->name has been set. Fixes #466183 (on_showall_changed): actually get the GConfValue.
*** Bug 473943 has been marked as a duplicate of this bug. ***
Looks like that's still buggy on GNOME 2.20.0
The reporter is using the wrong gconf key, it's "showall", not "show_all", seems to be a typo in the help docs, bug gconf-editor would have shown the right key anyways. I've fixed the typo in the unstable branch.
(In reply to comment #4) > The reporter is using the wrong gconf key, it's "showall", not "show_all", > seems to be a typo in the help docs, bug gconf-editor would have shown the > right key anyways. I've fixed the typo in the unstable branch. I've requested the submitter to reconfirm the key name he used; thanks.
(In reply to comment #4) > The reporter is using the wrong gconf key, it's "showall", not "show_all", > seems to be a typo in the help docs, bug gconf-editor would have shown the > right key anyways. I've fixed the typo in the unstable branch. Actually I tried with showall and it doesn't work for me either; reopening the bug here.
Ah! It works when setting the GConf key as root! The menu entry is configured to be run within "gksu"; if I run it as a normal user, I get: "The configuration could not be loaded" "You are not allowed to access the system configuration". Is it supposed to be run as a normal user?
right! oh, the wonders of gksu, thanks Loïc for noticing that :) In the current default setup, system-tools-backends uses DBus policies to allow accessing the configuration to the root user and people in stb-group (obviously, the group can be modified by passing --with-stb-group=foo to s-t-b configure). The rest of the users should get that dialog when trying to access the configuration. the policy to access the backends are stored in /etc/dbus-1/system.d/system-tools-backends.conf Given this, it's ok to close again? :), using gksu is a distro decision, not upstream's
Oh sure; as gksu is not an upstream decision, I'm closing this bug again with the initial resolution; thanks!
BTW, saw the launchpad comments, I'm already working on optional PolicyKit support for 2.21.x, It'd be great to see PolicyKit being used in Gutsy+1 :)
Cool, I also added another proposed workaround which would be to "sg" instead of "su" to root. But the clean solution is clearly PolicyKit; thanks for your input.