Bug 508655 - get_default_keyring_sync() throws error when no keyring present
get_default_keyring_sync() throws error when no keyring present
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gnome-python2-desktop (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Matthew Barnes
Depends On:
  Show dependency treegraph
Reported: 2009-06-29 06:58 EDT by Vladimir Benes
Modified: 2015-08-03 08:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-06-02 09:22:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vladimir Benes 2009-06-29 06:58:18 EDT
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.
program is killed without exception :(

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

How reproducible:

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

Expected results:
catchable exception

Additional info:
Comment 1 RHEL Product and Program Management 2009-11-06 14:19:43 EST
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 Product and Program Management 2014-03-07 08:53:29 EST
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 Product and Program Management 2014-06-02 09:22:00 EDT
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).

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