Bug 580180 - [abrt] crash in gnupg2-2.0.14-2.fc13: Process /usr/bin/gpgkey2ssh was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnupg2-2.0.14-2.fc13: Process /usr/bin/gpgkey2ssh was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 669570
Alias: None
Product: Fedora
Classification: Fedora
Component: gnupg2
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9b74792ed1db0aa56935d554474...
: 606446 637380 650426 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-07 16:30 UTC by Bernie Innocenti
Modified: 2011-09-20 08:47 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-09-20 08:47:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (3.89 KB, text/plain)
2010-04-07 16:30 UTC, Bernie Innocenti
no flags Details

Description Bernie Innocenti 2010-04-07 16:30:45 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gpgkey2ssh
component: gnupg2
executable: /usr/bin/gpgkey2ssh
kernel: 2.6.33.1-19.fc13.x86_64
package: gnupg2-2.0.14-2.fc13
rating: 4
reason: Process /usr/bin/gpgkey2ssh was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
Just execute gpgkey2ssh without arguments.

It should do something more useful than dumping core, such as printing a help message.

Comment 1 Bernie Innocenti 2010-04-07 16:30:48 UTC
Created attachment 405021 [details]
File: backtrace

Comment 2 Tomas Mraz 2010-04-07 17:16:38 UTC
This is not a segfault but assertion abort. Such requests would be best handled by communicating with the upstream developers directly.

I've created a report in upstream issue tracker: https://bugs.g10code.com/gnupg/issue1210

Comment 3 Karel Klíč 2010-11-09 13:23:12 UTC
*** Bug 606446 has been marked as a duplicate of this bug. ***

Comment 4 Karel Klíč 2010-11-09 13:23:18 UTC
*** Bug 637380 has been marked as a duplicate of this bug. ***

Comment 5 Karel Klíč 2010-11-09 13:23:23 UTC
*** Bug 650426 has been marked as a duplicate of this bug. ***

Comment 6 Bug Zapper 2011-06-02 15:37:03 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bernie Innocenti 2011-06-02 15:46:35 UTC
Still happens in F14.

Comment 8 Tomas Mraz 2011-09-20 08:47:28 UTC

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


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