Bug 650426

Summary: [abrt] gnupg2-2.0.14-7.fc13: raise: Process /usr/bin/gpgkey2ssh was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Philippe Miossec <pmiossec>
Component: gnupg2Assignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bcl, nalin, rdieter, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1b71d38717708d466e9092b68f4ca9d760b2ae47
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 13:23:23 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 Philippe Miossec 2010-11-06 10:30:56 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gpgkey2ssh 4289D98B3A8C7107
component: gnupg2
crash_function: raise
executable: /usr/bin/gpgkey2ssh
kernel: 2.6.34.7-61.fc13.i686
package: gnupg2-2.0.14-7.fc13
rating: 4
reason: Process /usr/bin/gpgkey2ssh was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1289037647
uid: 500

comment
-----
Surely not the better solution but the problem come from the fact that's the gnupg2 package that is installed.

To correct the problem, the command "ln -s gpg2 gpg" works.

So please fix the gpgkey2ssh file to look for the gpg2 command (which is in the same package) and not the gpg command.

How to reproduce
-----
1. Launch gpgkey2ssh
2. the program crash after displaying : "sh: gpg: command not found"
Comment 1 Philippe Miossec 2010-11-06 10:30:59 UTC 
Created attachment 458306 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:23:23 UTC 

*** This bug has been marked as a duplicate of bug 580180 ***
Comment 3 Karel Klíč 2010-11-09 13:23:23 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 #580180.

Sorry for the inconvenience.