Bug 603265 - system-config-users errors on deleting user
Summary: system-config-users errors on deleting user
Status: CLOSED DUPLICATE of bug 602192
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-users   
(Show other bugs)
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-12 05:50 UTC by Bruce Brackbill
Modified: 2010-06-14 08:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-14 08:55:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
system-config-users Delete User Dialog (31.33 KB, image/png)
2010-06-12 05:50 UTC, Bruce Brackbill
no flags Details

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
  File "/usr/share/system-config-users/mainWindow.py", line 890, in rmrf
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 ***

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