Bug 161339 - redhat-config-users crashs when you change name of root
redhat-config-users crashs when you change name of root
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-config-users (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nils Philippsen
Depends On: 105632
  Show dependency treegraph
Reported: 2005-06-22 11:16 EDT by Nils Philippsen
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:59:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nils Philippsen 2005-06-22 11:16:51 EDT
+++ This bug was initially created as a clone of Bug #105632 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030530

Description of problem:
If you try to change the username of "root" the program will crash. It locks up
and prints some errors to the terminal (if you ran it from there).

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

How reproducible:

Steps to Reproduce:
1. Run "redhat-config-users" in a term
2. Unfilter the system users
3. Go to properties of "root"
4. Change the root username to any other name.

Actual Results:  Locks up, it does change the name of root but many other things
start to fail at that point.

Expected Results:  Not sure honestly, either it should work cleanly or not allow
it in the first place.

Additional info:
Comment 1 RHEL Product and Program Management 2007-10-19 14:59:39 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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