Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 158595 - Application crashes upon right-clicking on a keyring
Summary: Application crashes upon right-clicking on a keyring
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gnome-keyring-manager
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Tomáš Bžatek
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-23 20:34 UTC by Jason Bradley Nance
Modified: 2015-03-03 22:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-20 16:00:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jason Bradley Nance 2005-05-23 20:34:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
Gnome keyring manager crashes when right-clicking on any keyring in the list.

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

How reproducible:

Steps to Reproduce:
1.Login to Gnome
2.Open up "Keyring Manager" from Applications->System Tools
3.Right-click on a keyring in the list

Actual Results:  Application crashes.

Expected Results:  Application should not crash.  Context menu should appear if applicable.

Additional info:

Comment 1 Alexander Larsson 2005-05-24 06:58:57 UTC
I'm not sure why i got this bug. Anyway, david, I think this is fixed in later

Comment 2 Jiri Pallich 2012-06-20 16:00:42 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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