Bug 666207 - [abrt] dirmngr-1.1.0-1.fc14: strcmp: Process /usr/bin/dirmngr was killed by signal 11 (SIGSEGV)
Summary: [abrt] dirmngr-1.1.0-1.fc14: strcmp: Process /usr/bin/dirmngr was killed by s...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: dirmngr
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0f3190b6f5c2ea3db33a1d3a418...
: 669903 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-29 15:14 UTC by info@kobaltwit.be
Modified: 2011-12-24 09:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-12-24 09:57:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (6.35 KB, text/plain)
2010-12-29 15:14 UTC, info@kobaltwit.be 		no flags Details
View All

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. ***
Note You need to log in before you can comment on or make changes to this bug.