I maybe have found something in system-tools-backend which could explain this weird bug.
system-tools-backends looks at the line number instead of the group name to see if a group have been deleted/added/modified.
Just look at the set function in /usr/share/system-tools-backends-2.0/scripts/Users/Groups.pm
I won't go into details but this behaviour works correctly only the first time.
If you launch users-admin, delete a group and then create a new user (with a new group), system-tools-backends will try to delete another group and will try to rename several groups (which fail because the target group name already exists).
/usr/share/system-tools-backends-2.0/scripts/Users/Users.pm seems to behave the same.
I am not sure this is the cause of this bug, I still don't see in what conditions it could trigger this bug.
I maybe have found something in system- tools-backend which could explain this weird bug.
system- tools-backends looks at the line number instead of the group name to see if a group have been deleted/ added/modified. system- tools-backends- 2.0/scripts/ Users/Groups. pm
Just look at the set function in /usr/share/
I won't go into details but this behaviour works correctly only the first time.
If you launch users-admin, delete a group and then create a new user (with a new group), system- tools-backends will try to delete another group and will try to rename several groups (which fail because the target group name already exists).
/usr/share/ system- tools-backends- 2.0/scripts/ Users/Users. pm seems to behave the same.
I am not sure this is the cause of this bug, I still don't see in what conditions it could trigger this bug.