Bug 199836 - problems with group assignments for specific UID/GID requests
Summary: problems with group assignments for specific UID/GID requests
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-users
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-23 03:10 UTC by G.Wolfe Woodbury
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-07-24 16:18:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description G.Wolfe Woodbury 2006-07-23 03:10:10 UTC
Description of problem:

If I create a new group using a specific ID (e.g. boinc2=601) and then create
a user (e.g. boinc2=601) I get an error message that GID "None" is in use and
the creation will not take place.   This is a regression from previous behaviour
where this sequence would create a "properly" numbered UID/GID setup for a
user.


Version-Release number of selected component (if applicable):


How reproducible:
three days in a row on rawhide


Steps to Reproduce:
1. run system-config-users
2. create a new group with a specific GID
    (e.g. boinc2 = 601)
3. create a new user with a specific UID
    (e.g. boinc2 = 601)
4. observe an error message
  
Actual results:
error message as described.


Expected results:
a "properly" numbered UID/GID pair for the selected user.


Additional info:

fresh install (except for /home) of rawhide 2006-07-22 on i686 machine.

Comment 1 Nils Philippsen 2006-07-24 16:18:34 UTC
Should be fixed in system-config-users-1.2.46 which should hit the mirrors soon
(it's building right now), it asks the user what to do if a group with the same
gid or name already exists.

Please make a note of the package version you have in future bug reports (the
state of Rawhide isn't preserved, it would be difficult to find that info later).


Note You need to log in before you can comment on or make changes to this bug.