Bug 508655

Summary:	get_default_keyring_sync() throws error when no keyring present
Product:	Red Hat Enterprise Linux 5	Reporter:	Vladimir Benes <vbenes>
Component:	gnome-python2-desktop	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED WONTFIX	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.4	CC:	vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-02 13:22:00 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:

Description Vladimir Benes 2009-06-29 10:58:18 UTC

Description of problem:
I have empty keyring directory and gkey.get_default_keyring_sync() throws error like this: 
python: Objects/stringobject.c:105: PyString_FromString: Assertion `str != ((void *)0)' failed.
Aborted
program is killed without exception :(

Version-Release number of selected component (if applicable):
gnome-python2-gnomekeyring-2.16.0-3.el5

How reproducible:


Steps to Reproduce:
1.remove all keyrings from your ~/.gnome2/keyrings directory
2.run get_default_keyring_sync() 
3.
  
Actual results:
error and program Aborted

Expected results:
catchable exception

Additional info:

Comment 1 RHEL Program Management 2009-11-06 19:19:43 UTC

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 2 RHEL Program Management 2014-03-07 13:53:29 UTC

This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 3 RHEL Program Management 2014-06-02 13:22:00 UTC

Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).