Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 708919

Summary: [abrt] gnome-keyring-2.28.2-6.el6: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT)
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: gnome-keyringAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: case-diagnostics, m_roark, pingale, rdassen, tpelka, tsmetana, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gnome-keyring-2.28.2-7.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 14:04:51 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:
Bug Depends On: 745695    
Bug Blocks:    
Attachments:
Description Flags
Backtrace, Dissassembly none

Description Siddharth 2011-05-30 06:55:48 UTC 
Description of problem:
abrt version: 1.1.16
Attached file: backtrace, 35172 bytes
cmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
component: gnome-keyring
Attached file: coredump, 309702656 bytes
executable: /usr/bin/gnome-keyring-daemon
kernel: 2.6.32-131.0.15.el6.x86_64
rating: 0
reason: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT)
Attached file: sosreport.tar.xz, 1246804 bytes
time: 1306346850
uid: 500

customer comment
gsh is simply a Perl script from http://outflux.net/unix/software/gsh/ that allows to run commands on multiple hosts. gsh well running on RHEL4 but it does not work with RHEL6.1. When customer run gsh on RHEL6.1 gnome-keyring
crash.

How to reproduce
run gsh to run uptime command on different host

Version-Release number of selected component (if applicable):
architecture: x86_64
Red Hat Enterprise Linux Server release 6.1 (Santiago)
gnome-keyring-2.28.2-6.el6

Steps to Reproduce:
1. Log into GNOME
2. run "ssh-add"
3. run "gsh myhosts uptime
  
Actual results:
gnome-keyring crash 

Expected results:
gnome-keyring should not crash

Additional info:
Comment 1 Siddharth 2011-05-30 07:07:37 UTC 
Created attachment 501719 [details]
Backtrace, Dissassembly
Comment 5 RHEL Program Management 2011-07-06 00:37:11 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 8 Tomáš Bžatek 2011-10-17 13:54:11 UTC 
FYI, bug 745695 is about egg_secure_free_full(), could be the same issue.
Comment 11 RHEL Program Management 2011-12-19 17:20:12 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 13 Tomáš Bžatek 2012-02-28 13:27:47 UTC 
*** Bug 707708 has been marked as a duplicate of this bug. ***
Comment 17 errata-xmlrpc 2012-06-20 14:04:51 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0878.html