Failures happen at random points in the code when GNOME keyring is active but not accessible

Bug #743748 reported by Jelmer Vernooij
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python Keyring
New
Undecided
Unassigned
python-keyring (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: python-keyring

These situations all have in common that the GNOME keyring is active (so keyring tries to use it instead of falling back to KWallet or a file on disk), but when it comes time to actually use the keyring, something goes wrong:
a) the keyring turns out to be inaccessible, causing an error.
b) the keyring claims it can't find a key, even though it didn't look (the keyring was never unlocked, so it couldn't have looked).
c) the keyring library crashes when trying to write a new key to the keyring.
d) the keyring hangs when it should be presenting a GUI for unlocking the keyring

(filing to track bug 40 upstream, filed by Leonard)

Revision history for this message
Jelmer Vernooij (jelmer) wrote :
Revision history for this message
Sebastian Ramacher (s-ramacher) wrote :

As noted in the upstream bug report, this should be fixed by 2.1+. Please reopen the bug if it's still an issue.

Changed in python-keyring (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.