Crash on start if default keyring is locked
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Polly |
New
|
Undecided
|
Unassigned |
Bug Description
For some reason, my default keyring is not unlocked automatically when I login.
So, if I start Polly before unlocking it, Polly crashes with the following stacktrace:
$ polly
Polly 0.93.11 (pre-alpha 3.11)
Copyright (C) 2011 Marcelo Hashimoto
cache path: /home/lorentz/
config path: /home/lorentz/
data home: /home/lorentz/
initializing...
Traceback (most recent call last):
File "/usr/bin/polly", line 303, in <module>
account_manager = gui.twitter.
File "/usr/lib/
subtoken_secret = keyring.
File "/usr/lib/
return _keyring_
File "/usr/lib/
collection = self.get_
File "/usr/lib/
if collection.
File "/usr/lib/
return exec_prompt_
File "/usr/lib/
from gi.repository import GLib
File "/usr/lib/
from ._gi import _API
ImportError: cannot import name _API
If I unlock the keyring with Seahorse, then Polly works fine.
I will confirm this later at home, but IIRC python-keyring indeed assumes that the chosen keyring is unlocked.
But what is weird is that the error message does not seem directly related to that, but to the fact that PyGI is incompatible with PyGTK2. Why is this error not being triggered when the keyring is unlocked? Does it use an older library in that case? Does not make sense, I need to check that out...
Oh, and which distro are you using?