Bug 586267

Summary: crash in accountsdialog-0.6-3.fc13 when deleting a standard user, and choosing delete their files
Product: [Fedora] Fedora Reporter: Rodrigo Ayala <rayalac>
Component: accountsdialogAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:d0c4ee549a84c9c7332ffd3f71cc18fe96eed0a9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 09:35:47 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
File: backtrace none

Description Rodrigo Ayala 2010-04-27 07:46:41 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: accounts-dialog
comment: accountsdialog doesn't work properly. If you create any user with "standard" account type, and then you try to delete it, but trying to delete their files, the program exits unexpectedly.
component: accountsdialog
executable: /usr/bin/accounts-dialog
global_uuid: d0c4ee549a84c9c7332ffd3f71cc18fe96eed0a9
kernel: 2.6.33.2-57.fc13.i686.PAE
package: accountsdialog-0.6-3.fc13
rating: 4
reason: Process /usr/bin/accounts-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Go to Users in System, Administration.
2. Create any User with "Standard" account type
3. Try to delete that User, and when it asks "Do you want to keep User's files?", choose "Delete Files"-
Comment 1 Rodrigo Ayala 2010-04-27 07:46:43 UTC 
Created attachment 409390 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:35:47 UTC 

*** This bug has been marked as a duplicate of bug 582900 ***
Comment 3 Karel Klíč 2010-05-25 09:35:47 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #582900.

Sorry for the inconvenience.