Bug 651469

Summary: [abrt] gpa-0.9.0-1.fc14: Process /usr/bin/gpa was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: bethebeast <bethebeast>
Component: gpaAssignee: Orphan Owner <extras-orphan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: nalin, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:13c5dbde643f6206c774d55419f1f84b70c5d60b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:41:43 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 bethebeast 2010-11-09 16:27:20 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gpa
component: gpa
crash_function: gpa_gen_key_simple_operation_backup_complete
executable: /usr/bin/gpa
kernel: 2.6.35.6-48.fc14.x86_64
package: gpa-0.9.0-1.fc14
rating: 4
reason: Process /usr/bin/gpa was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289319969
uid: 500

How to reproduce
-----
1. try to generate a key for the first time
2. get crash
3.
Comment 1 bethebeast 2010-11-09 16:27:22 UTC 
Created attachment 459177 [details]
File: backtrace
Comment 2 bethebeast 2010-11-10 09:43:05 UTC 
Package: gpa-0.9.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. try to generate a key for the first time
2. get crash
3.


Comment
-----
every time i try to generate a gpg key, i get this crash
Comment 3 abrt-bot 2012-03-21 14:41:43 UTC 
Backtrace analysis found this bug to be similar to bug #703866, closing as duplicate.

Bugs which were found to be similar to this bug: bug #546702, bug #557979, bug #592560, bug #629927, bug #703866

This comment is automatically generated.

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