Bug 694419

Summary: [abrt] seahorse-2.28.1-4.el6: vfprintf: Process /usr/bin/seahorse was killed by signal 11 (SIGSEGV)
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: seahorseAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: cww, jwest, syeghiay, tsmetana, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-25 16:45:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Backtrace, Dissassembly none

Description Siddharth 2011-04-07 10:10:57 UTC 
Description of problem:

abrt version: 1.1.13
Attached file: backtrace
cmdline: seahorse
component: seahorse
crash_function: vfprintf
executable: /usr/bin/seahorse
kernel: 2.6.32-71.18.2.el6.x86_64
rating: 2
reason: Process /usr/bin/seahorse was killed by signal 11 (SIGSEGV)
time: 1301246788
uid: 501


Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux Client release 6.0 (Santiago)
seahorse-2.28.1-4.el6
architecture: x86_64


How reproducible:
Random Crash

Steps to Reproduce:
1.
2.
3.
  
Actual results:
seahorse was killed

Expected results:
seahorse should not killed

Additional info:
Comment 1 Siddharth 2011-04-07 10:15:10 UTC 
Created attachment 490506 [details]
Backtrace, Dissassembly
Comment 2 Tomáš Bžatek 2011-04-14 12:13:07 UTC 
I'm sorry, but from the backtrace attached it's not 100% clear where the crash actually was. Please specify steps to reproduce.