From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040623 Description of problem: Deleting an existing user from the Users and Groups System Settings tool doesn't purge /tmp of the users gnome related directories. This causes major problems if the same username is recreated later and assigned a different user and group id number. The resulting new user account will be unable to login using the gnome desktop until the old accounts directories in /tmp are deleted (gconfd-olduser, orbit-olduser, etc). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. within the Users and Account System Settings tool create a useraccount named 'olduser' 2. login to the gnome desktop using the 'olduser' account 3. logout of the gnome desktop and login with another account. 4. within the Users and Account System Settings tool delete the useraccount named 'olduser' as well as its home directory 5. within the Users and Account System Settings tool recreate the 'olduser' user account but assign it a different user id number than before 6. attempt to login to the gnome desktop using the recreated 'olduser' account Actual Results: The gnome desktop is unable to properly load for the recreated 'olduser' account with the new user id. This is because stale gnome related directories are left in /tmp. These old gnome related directories in /tmp should be deleted have been deleted by the Users and Group tool when it deleted the user account originally. Expected Results: I expected that a newly recreated 'olduser' account with a different user id to work without hunting for old gnome related directories in /tmp. Additional info:
fixed in system-config-users-1.2.27 and later
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-440.html