Bug 220679 - system-config-users aborts when freeing invalid pointer
system-config-users aborts when freeing invalid pointer
Product: Fedora
Classification: Fedora
Component: libuser (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Depends On:
  Show dependency treegraph
Reported: 2006-12-22 19:03 EST by Jukka Ketelaars
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-06 16:00:54 EST
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 Jukka Ketelaars 2006-12-22 19:03:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061027 Firefox/2.0

Description of problem:
When using system-config-users to create a new user the dialog freezes after pressing the ok button. 

When running it from the command line the following error is displayed:
# system-config-users 
*** glibc detected *** /usr/bin/python2: free(): invalid pointer: 0x082560b0 ***

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

How reproducible:

Steps to Reproduce:
1. start system-config-users from command line
2. Press "Add user"
3. User name: test
4. Full name: Test
5. Password/Confirm password: some password
6. Press OK

Actual Results:
The gui freezes and the following error is printed:
*** glibc detected *** /usr/bin/python2: free(): invalid pointer: 0x082560b0 ***

Expected Results:
user should have been created.

Additional info:
Comment 1 Nils Philippsen 2006-12-27 10:50:11 EST
changing component to python
Comment 2 Jeremy Katz 2007-01-06 16:00:54 EST
This is being caused by libuser allocating memory with PyObject_Malloc and then
freeing it with PyMem_DEL.  In python 2.5, these actually have a differences (so
that the interpreter can return memory to the system).

Fixed in libuser-0.55-2

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