Description of problem: Version-Release number of selected component (if applicable): autokey-gtk-0.90.4-2.fc18.noarch How reproducible: 100% Steps to Reproduce: 1.run autokey-gtk 2.observe error message 3.sigh disappointedly Actual results: prints "gi.RepositoryError: Requiring namespace 'Gtk' version '2.0', but '3.0' is already loaded" and exits Expected results: runs Additional info:
Complete error output: Traceback (most recent call last): File "/bin/autokey-gtk", line 20, in <module> from autokey.gtkapp import Application File "/usr/lib/python2.7/site-packages/autokey/gtkapp.py", line 31, in <module> from gtkui.configwindow import ConfigWindow File "/usr/lib/python2.7/site-packages/autokey/gtkui/configwindow.py", line 20, in <module> from gi.repository import Gtk, Pango, GtkSource, Gdk, Gio File "/usr/lib/python2.7/site-packages/gi/importer.py", line 76, in load_module dynamic_module._load() File "/usr/lib/python2.7/site-packages/gi/module.py", line 242, in _load version) File "/usr/lib/python2.7/site-packages/gi/module.py", line 97, in __init__ repository.require(namespace, version) gi.RepositoryError: Requiring namespace 'Gtk' version '2.0', but '3.0' is already loaded
This still exists in Fedora 19: Bug 1008008
On Fedora 19, I was able to resolve this by installing gtksourceview3. I no longer have a Fedora 18 install to test on, but I'm certain it's the same fix here.
autokey-0.90.4-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/autokey-0.90.4-3.fc18
Package autokey-0.90.4-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing autokey-0.90.4-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16929/autokey-0.90.4-3.fc18 then log in and leave karma (feedback).
autokey-0.90.4-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.