Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 107991 - redhat-config-users leaves a frozen dialog after pressing "Cancel"
Summary: redhat-config-users leaves a frozen dialog after pressing "Cancel"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: redhat-config-users
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-10-25 19:34 UTC by petrosyan
Modified: 2007-04-18 16:58 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-10-27 19:21:10 UTC
Embargoed:


Attachments (Terms of Use)

Description petrosyan 2003-10-25 19:34:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031023

Description of problem:
redhat-config-users leaves a frozen dialog after pressing "Cancel"

Version-Release number of selected component (if applicable):
redhat-config-users-1.2.3-1

How reproducible:
Always

Steps to Reproduce:
1. start redhat-config-users
2. click on the "Add Group" button
3. enter "test123" in the "Group name:" input field
4. press "OK" button
5. press "Add User" button
6. Enter "User Name:" test123, "Full Name:" doesnt matter, "Password:"
password_here, "Confirm Password:" password_here . Don't change any of the
default settings.
7. press "OK" button
8. you will be presented with a dialog: "A group with this name already exists.
What would you like to do? (*) Add to the existing group ( ) Add to the 'users'
gourp" . Press "Cancel" button in that dialog.
9. "Create New User Dialog" stays on the screen in a frozen state.

Comment 1 Brent Fox 2003-10-27 19:21:10 UTC
Ah, I needed to call self.ready() to counteract the self.busy() call at the
beginning of the function.  Should be fixed in redhat-config-users-1.2.4-1. 
Thanks for your report.


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