karmic has seen the end of its life and is no longer receiving any
updates. Marking the karmic task for this ticket as 'Won't Fix'.
** Changed in: gnome-system-tools (Ubuntu Karmic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Deskt
Fixed in lucid, thanks Milan!
If we have another g-s-t SRU in karmic, this can be slipped in, but I
think it's not serious enough to warrant the effort of an SRU by itself.
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged => Fix Released
** Also affects: gnome-system-tools (Ubun
Hm, silly: the latter is actually not in 2.29.1, but will be in the next
release. Anyway, that's for Lucid.
--
[users-admin] Group Properties dialog sets GID to 0 on first launch
https://bugs.launchpad.net/bugs/475974
You received this bug notification because you are a member of Ubuntu
Desktop B
Development version 2.29.1 contains the fix for the "GID is 0 on start"
problem, and also prevents you from choosing already used GIDs when
creating/editing groups.
** Changed in: gst
Status: Fix Committed => Fix Released
--
[users-admin] Group Properties dialog sets GID to 0 on first lau
** Changed in: gnome-system-tools (Ubuntu)
Status: Confirmed => Triaged
--
[users-admin] Group Properties dialog sets GID to 0 on first launch
https://bugs.launchpad.net/bugs/475974
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to g
The fix only contains the minimal changes we need to avoid giving users
admin rights. We try not to introduce important changes in stable
releases, and absolutely never change the user interface. I'll fix that
for the next release, that's quite easy to do actually.
As for the label of the button,
On the usability side of things - don't you agree the button called
'Manage Groups' is actually misleading when the user hasn't unlocked the
settings? There's nothing to manage after all.
IMHO, when the settings are locked, the button should be called 'View
Groups'. As soon as the user has unlocke
Milan, thanks for confirming my report. While you're at it, I hope the
fix also contains a check on the GID that's entered by the user when
adding a new group. If the GID exists, it should notify the user about
it (preferably in an elegant way) and should not just silently accept
(and ultimately fa
As reported in the duplicate bug 486130, this has more dramatic
consequences when creating a group: the GID is set to 0 by default,
which leads to adding users to the root group without notice. While
admins can be clever enough to change that, people may still miss this
detail, which could be highl
