Bug 426422 - Creating Numeric Only User Names During Firstboot fails (Throws exception, requesting Bug report)
Summary: Creating Numeric Only User Names During Firstboot fails (Throws exception, re...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-users
Version: 5.1
Hardware: i386
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Nils Philippsen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-20 21:58 UTC by Jonathan Jarrett
Modified: 2008-07-15 14:14 UTC (History)
0 users

Fixed In Version: system-config-users-1.2.51-4.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-15 14:14:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
The file request to be attached to bug report, by the system. (598 bytes, text/plain)
2007-12-20 21:58 UTC, Jonathan Jarrett
no flags Details

Description Jonathan Jarrett 2007-12-20 21:58:08 UTC
Description of problem:

Tried to create a user during firstboot with a user name consisting of only
numeric characters.  Dialog warning about confusion which may ensue opened, with
only 'OK' as option.  Clicking 'OK' dismisses dialog, and then system opened
error dialog with details, requesting the attached file be sent and bug report made.

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


How reproducible:


Steps to Reproduce:
1. Install OS
2. When firstboot asks for new user create one with numeric characters only
3.
  
Actual results:

exception throw user not created.

Expected results:

either user created as requested or able to go back to that step and create
another user with a valid (non-numeric only) user name.


Additional info:

Comment 1 Jonathan Jarrett 2007-12-20 21:58:08 UTC
Created attachment 290196 [details]
The file request to be attached to bug report, by the system.

Comment 3 Nils Philippsen 2008-07-15 14:14:36 UTC
Should be fixes in system-config-users-1.2.51-4.el5 already. Next time, please
provide the requested version/release of the component, thanks!

Please report back if this version doesn't fix the problem (it worked for me).


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