Bug 112388 - redhat-config-users fails with several errors
redhat-config-users fails with several errors
Status: CLOSED NEXTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-users (Show other bugs)
8.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Brent Fox
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-18 15:11 EST by Darren Gitelman
Modified: 2007-04-18 13:00 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-12-18 22:25:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Darren Gitelman 2003-12-18 15:11:09 EST
Description of problem:
Multiple errors when trying to run redhat-config-users
1) First error occurs when trying to start it. The traceback is below.
Despite these errors the gui opens:

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 245
(extract_id): assertion `array != NULL' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 1100
(lu_dispatch): assertion `ldata != INVALID' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 245
(extract_id): assertion `array != NULL' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 1100
(lu_dispatch): assertion `ldata != INVALID' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 245
(extract_id): assertion `array != NULL' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 1100
(lu_dispatch): assertion `ldata != INVALID' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 245
(extract_id): assertion `array != NULL' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 1100
(lu_dispatch): assertion `ldata != INVALID' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 245
(extract_id): assertion `array != NULL' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 1100
(lu_dispatch): assertion `ldata != INVALID' failed
-----------------------


2) Second error occurs when selecting a user and trying to manipulate
properties. Upon Clicking OK in a properties dialog the following
error appears. Once that happens redhat-config-users main window grays
out.

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 245
(extract_id): assertion `array != NULL' failed

** (redhat-config-users.py:28242): CRITICAL **: file user.c: line 1100
(lu_dispatch): assertion `ldata != INVALID' failed
Traceback (most recent call last):
  File "/usr/share/redhat-config-users/userProperties.py", line 418,
in on_ok_button_clicked
    self.parent.refresh_users_and_groups(need_refresh)
  File "/usr/share/redhat-config-users/mainWindow.py", line 398, in
refresh_users_and_groups
    gidNumber = gidNumber[0]
IndexError: list index out of range

-----------------------

I read through bugzilla and found that if /etc/passwd and /etc/shadow
were out of sync that could generate trouble. So I looked through both
files and the order of users is the same. Then I copied the
/etc/passwd, /etc/shadow, and /etc/group files from another one of our
machines on which redhat-config-users was working. That made no
difference. The errors still occurred on this machine.


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

How reproducible:
Always

Steps to Reproduce:
1. start redhat-config-users from command line.
2. try to edit properties of a user
3.
  
Actual results:
Application fails

Expected results:
Application should work.

Additional info:
Comment 1 Darren Gitelman 2003-12-18 22:25:21 EST
I resolved the bug by finding that my gshadow and group file were out
of sync. In some future release it would be helpful if
redhat-config-users informed the user when files were not in sync.
e.g., found user "baduser" in passwd but not in shadow, or found group
"badgroup" in group but not in gshadow. Then at least the user would
know what to do.

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