Description of problem: I was attempting to debug why gnomekeyring kept throwing errors in some code I was working with, so I went back to the basics to understand how it worked. I looked at gnome-python-desktop-2.29.1/examples/keyring.py, which seems to match up to the code I had, but when I tried to execute it, it fails in the same way: [spot@pterodactyl examples]$ ./keyring.py Traceback (most recent call last): File "./keyring.py", line 94, in <module> login, password = get_login_password() File "./keyring.py", line 87, in get_login_password "\n".join((login, password)), True) gnomekeyring.BadArgumentsError Version-Release number of selected component (if applicable): gnome-keyring-2.29.5-1.fc13.x86_64 gnome-python2-gnomekeyring-2.29.1-3.fc13.x86_64 How reproducible: Everytime Steps to Reproduce: 1. Run gnome-python-desktop-2.29.1/examples/keyring.py 2. In the gtk box that opens, input a login and password (the data is irrelevant) 3. Watch it crash on the console. Actual results: Crash. Expected results: "login: %s; password: %s" printed to console
Interesting, it appears to work fine on Fedora 12. Need to find a Rawhide machine to debug this...
Finally found a Rawhide machine to debug this, but I'm not even getting as far as you: $ ./keyring.py Traceback (most recent call last): File "./keyring.py", line 94, in <module> login, password = get_login_password() File "./keyring.py", line 18, in get_login_password keyring = gnomekeyring.get_default_keyring_sync() gnomekeyring.IOError Smells like a D-Bus issue to me. I'm told gnome-keyring is kind of broken right now anyway since the libgnome-keyring split in 2.29.4, and I don't know if that involved any API changes. May just need to wait for the keyring to be fixed and/or updated bindings.
Closing this as a duplicate of bug #558678 since it looks like the issue is in gnome-keyring itself, not the Python bindings. *** This bug has been marked as a duplicate of bug 558678 ***
ah. I *did* look for dupes, but not filed against other components :/ sorry.