breaks application when Gtk3 is also used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Python Keyring |
Fix Released
|
High
|
Unassigned | ||
python-keyring (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
keyring imports the gnomekeyring module, which uses gtk2.
This breaks any Gtk3 applications in which it is loaded.
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import keyring
>>> from gi.repository import GOBject
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/
from ._gi import _API, Repository
ImportError: could not import gobject (error was: ImportError('When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject".',))
I'm not sure what the best solution is to work around this - it seems pretty hard to determine if the current application is a gtk2 or gtk3 app, especially if keyring is imported before Gtk. It would be nice if there was at least some way of disabling the GNOME backend for keyring, so applications that are aware of this issue can work around it.
Changed in python-keyring: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Jelmer Vernooij (jelmer) |
status: | Triaged → In Progress |
Changed in python-keyring: | |
assignee: | Jelmer Vernooij (jelmer) → nobody |
Changed in python-keyring: | |
status: | In Progress → Fix Committed |
Changed in python-keyring (Ubuntu): | |
status: | Confirmed → Fix Released |
https:/ /bitbucket. org/kang/ python- keyring- lib/issue/ 52/breaks- gtk3-applicatio ns