Bug 663578 - [abrt] gpa-0.9.0-1.fc14: Process /usr/bin/gpa was killed by signal 11 (SIGSEGV)
Summary: [abrt] gpa-0.9.0-1.fc14: Process /usr/bin/gpa was killed by signal 11 (SIGSEGV)
Keywords:
Status: CLOSED DUPLICATE of bug 642115
Alias: None
Product: Fedora
Classification: Fedora
Component: gpa
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e3ecc73dae629753e07fd0a338d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-16 09:14 UTC by Jochan
Modified: 2010-12-20 13:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-20 13:57:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (12.07 KB, text/plain)
2010-12-16 09:14 UTC, Jochan
no flags Details

Description Jochan 2010-12-16 09:14:41 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gpa
comment: Nothing...Program was reporting some errors from the start
component: gpa
crash_function: gpa_gen_key_simple_operation_backup_complete
executable: /usr/bin/gpa
kernel: 2.6.35.9-64.fc14.i686
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: 1292336816
uid: 500

How to reproduce
-----
1.Install the gpa
2.
3.

Comment 1 Jochan 2010-12-16 09:14:44 UTC
Created attachment 469102 [details]
File: backtrace

Comment 2 Jediah Logiodice 2010-12-20 02:51:34 UTC
Package: gpa-0.9.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Install GnuPG
2. Install GPA
3. Run GPA
4. Get Exception stating "GPGME: Invalid Crypto Engine"
5. Once you clear this error - create new key
6. while key is being backed up - this exception will be thrown


Comment
-----
I'm not sure I can reproduce it without uninstalling and reinstalling, because now the "GPGME: Invalid Crypto Engine" will not go away, every time I click "close" it pops up over and over again.

Comment 3 Gwyn Ciesla 2010-12-20 13:57:41 UTC

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


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