Bug 603265

Summary: system-config-users errors on deleting user
Product: [Fedora] Fedora Reporter: Bruce Brackbill <brackbillbruce>
Component: system-config-usersAssignee: Nils Philippsen <nphilipp>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: nphilipp
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-14 08:55:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
system-config-users Delete User Dialog none

Description Bruce Brackbill 2010-06-12 05:50:59 UTC
Created attachment 423440 [details]
system-config-users Delete User Dialog

Description of problem:

When I attempt to delete a user with system-config-users the dialog comes up and I press yes and the following error appears in the console.

[root@localhost ~]# system-config-users
Traceback (most recent call last):
  File "/usr/share/system-config-users/mainWindow.py", line 710, in on_delete_activate
    self.rmrf(mailSpool)
  File "/usr/share/system-config-users/mainWindow.py", line 890, in rmrf
    raise
TypeError: exceptions must be classes or instances, not NoneType
[root@localhost ~]# 

The user's home directory IS deleted but the only way to close the dialog is to X out of it.

The user frank still exists and when I bring up the Delete dialog again the dialog is different saying: "I won't delete frank <snip> direcory does not exist".  ( See attached image ).  This dialog successfully closes and The user frank is deleted. 

system-config-users-1.2.98-1.fc13.noarch and everything updated.  Testing repo enabled.

Comment 1 Nils Philippsen 2010-06-14 08:55:35 UTC
I've already fixed this and issued an update but it hasn't been pushed to testing yet.

*** This bug has been marked as a duplicate of bug 602192 ***