← Back to team overview

desktop-packages team mailing list archive

[Bug 26338] Re: Changing users randomly affects other users and group memberships

 

** Tags added: mago

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/26338

Title:
  Changing users randomly affects other users and group memberships

Status in The Gnome System Tools:
  Fix Released
Status in Ubuntu:
  Invalid
Status in “gnome-system-tools” package in Ubuntu:
  Fix Released
Status in The Dapper Drake:
  Invalid
Status in “gnome-system-tools” source package in Dapper:
  Invalid
Status in The Edgy Eft:
  Invalid
Status in “gnome-system-tools” source package in Edgy:
  Fix Released
Status in The Feisty Fawn:
  Invalid
Status in “gnome-system-tools” source package in Feisty:
  Fix Released
Status in The Gutsy Gibbon:
  Invalid
Status in “gnome-system-tools” source package in Gutsy:
  Fix Released
Status in The Hardy Heron:
  Invalid
Status in “gnome-system-tools” source package in Hardy:
  Fix Released

Bug description:
  Impact:
  gnome-system-tools does not keep its internal model of users and groups consistent with the real world in /etc/passwd, /etc/shadow, and /etc/group. This leads to errors like deleting a different user than the one you chose in the UI, dropping unrelated users from groups like admin (thus making the system inaccessible for administration), and similar effects.

  Fix:
  Update the internal world model with each operation, done in http://svn.gnome.org/viewvc/gnome-system-tools?view=revision&revision=4017. This needs some serious backporting for Feisty and earlier, I suppose; it should apply well to Gutsy.

  Regression potential: The bug could not be fixed fully, there might be
  more places which need update calls. Potentially the patch could mess
  up the pam db even more.

  TEST CASE:
  1. launch users-admin
  2. create a test1 user
  3. create a test2 user (with admin rights)
  4. create a test3 user
  5. delete the test1 user
  6. delete the test3 user

  This will either cause test2 to not be in group admin any more, or be
  deleted in step 6 instead of user test3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst/+bug/26338/+subscriptions