Bug 666207

Summary: [abrt] dirmngr-1.1.0-1.fc14: strcmp: Process /usr/bin/dirmngr was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: info <info>
Component: dirmngrAssignee: Rex Dieter <rdieter>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: rdieter, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:0f3190b6f5c2ea3db33a1d3a418494663abc0dc2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-24 09:57:16 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 info@kobaltwit.be 2010-12-29 15:14:16 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: dirmngr --server
component: dirmngr
crash_function: strcmp
executable: /usr/bin/dirmngr
kernel: 2.6.35.10-74.fc14.i686.PAE
package: dirmngr-1.1.0-1.fc14
rating: 4
reason: Process /usr/bin/dirmngr was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1293635328
uid: 500

How to reproduce
-----
1. Find a pkcs12 certificate on your system
2. Right-click it and choose Open With Kleopatra
3. Kleopatra runs some self-tests which seemed ok, except for gpg-agent
4. Afterwards I found this backtrace via Abrt
Comment 1 info@kobaltwit.be 2010-12-29 15:14:18 UTC 
Created attachment 471070 [details]
File: backtrace
Comment 2 info@kobaltwit.be 2011-12-24 09:57:16 UTC 
I remember having frequent dirmngr crashes on Fedora 14 and I think also on F15.

I'm now running F16 and I haven't seen this abrt report abrt in quite a while.

So I suppose the bug can be closed. If you don't agree, feel free to reopen.
Comment 3 info@kobaltwit.be 2011-12-24 09:59:06 UTC 
*** Bug 669903 has been marked as a duplicate of this bug. ***