Bug 678148 - [abrt] accountsdialog-0.6-3.fc14: Process /usr/bin/accounts-dialog was killed by signal 11 (SIGSEGV)
Summary: [abrt] accountsdialog-0.6-3.fc14: Process /usr/bin/accounts-dialog was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 665804
Alias: None
Product: Fedora
Classification: Fedora
Component: accountsdialog
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6be0ca9011747098e42246f539c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 21:39 UTC by Edward Rudd
Modified: 2012-03-20 15:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:59:42 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (41.67 KB, text/plain)
2011-02-16 21:39 UTC, Edward Rudd 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Edward Rudd 2011-02-16 21:39:38 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: accounts-dialog
comment: If I click the "lock" and authenticate first, then it does not crash when clicking the account type (to change it)
component: accountsdialog
executable: /usr/bin/accounts-dialog
kernel: 2.6.35.11-83.fc14.x86_64
package: accountsdialog-0.6-3.fc14
reason: Process /usr/bin/accounts-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297892293
uid: 13183

How to reproduce
-----
1. Ran accounts-dialog
2. Clicks the the "Supervisor" text next to "Account Type"
Comment 1 Edward Rudd 2011-02-16 21:39:39 UTC 
Created attachment 479215 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 15:59:42 UTC 
Backtrace analysis found this bug to be similar to bug #665804, closing as duplicate.

Bugs which were found to be similar to this bug: bug #637168, bug #665804

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 665804 ***
Note You need to log in before you can comment on or make changes to this bug.