gwibber crashed with NoKeyringDaemonError in get_data()

[Jack]

Binary package hint: gwibber

Appears when trying to enter either Twitter or Identi.ca username and passwords. Can't close the dialog once crash has occur except by cross.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 0.8-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with NoKeyringDaemonError in get_data()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[André Gondim (andregondim)]

I saw this message error:

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/__init__.py", line 46, in get_data
    for message in method(client):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 207, in responses
    for data in self.get_replies():
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 181, in get_replies
    urllib.urlencode({"count": self.account["receive_count"] or "20"})))
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 161, in connect
    url, data, {"Authorization": self.get_auth()})).read()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 157, in get_auth
    ("%s:%s" % (self.account["username"], self.account["private:password"]))).strip()
  File "/usr/lib/python2.6/dist-packages/gwibber/config.py", line 57, in __getitem__
    {"id": "%s/%s/%s" % (self.path, self.id, key)})[0].secret
NoKeyringDaemonError

[André Gondim (andregondim)]

And this:

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/__init__.py", line 46, in get_data
    for message in method(client):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 216, in receive
    for data in self.get_messages():
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 166, in get_messages
    urllib.urlencode({"count": self.account["receive_count"] or "20"})))
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 161, in connect
    url, data, {"Authorization": self.get_auth()})).read()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 157, in get_auth
    ("%s:%s" % (self.account["username"], self.account["private:password"]))).strip()
  File "/usr/lib/python2.6/dist-packages/gwibber/config.py", line 57, in __getitem__
    {"id": "%s/%s/%s" % (self.path, self.id, key)})[0].secret
NoKeyringDaemonError

[André Gondim (andregondim)]

I'm using Ubuntu 9.04 Alpha 6 and Gwibber Version 0.8

Cheers.

[Martijn Cielen (mcielen)]

I have the same issue with Jaunty and Gwibber 0.8

[Arnaud Esquiva (insomniacs)]

Same issue... with jaunty beta 1.

[Andy Barilla (andybarilla)]

Same issue with jaunty beta 1 as of 4/2/2009

[Elaine Normandy (elainen)]

Same issue encountered after I deleted all .dotfiles in my home directory to be able to login after unrelated (I think) problem.

[Mathieu Marquer (slasher-fun)]

Confirming on gwibber(Ubuntu)

[Mathieu Marquer (slasher-fun)]

And that issue is also present with gwitter package from gwibber-team PPA (I know ubuntu launchpad is only about "official" packages, but that's just to let you know)

[Juanje Ojeda (juanje)]

This happens to me, but I think the problem was the gnome-keyring didn't launch at the begining of the session.

Once I've launched the gnome-keyring, the Gwibber let me create and use the accounts.

[Sebastien Bacher (seb128)]

the issue doesn't seem to be with gnome-keyring but rather with how gwibber use it

[Mathieu Marquer (slasher-fun)]

But with me gnome-keyring is actually running.

$ ps aux | grep keyring
root 22752 0.0 0.0 67788 1156 ? S 00:02 0:00 gnome-keyring-daemon

When launching gwibber :

$ gwibber

** (gwibber:23682): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-jmOtx0/socket: Connexion refusée

** (gwibber:23682): WARNING **: couldn't communicate with gnome keyring daemon via dbus: Failed to execute program gnome-keyring-daemon: Success

** (gwibber:23682): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-jmOtx0/socket: Connexion refusée

** (gwibber:23682): WARNING **: couldn't communicate with gnome keyring daemon via dbus: Failed to execute program gnome-keyring-daemon: Success

** (gwibber:23682): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-jmOtx0/socket: Connexion refusée

** (gwibber:23682): WARNING **: couldn't communicate with gnome keyring daemon via dbus: Failed to execute program gnome-keyring-daemon: Success

** (gwibber:23682): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-jmOtx0/socket: Connexion refusée

** (gwibber:23682): WARNING **: couldn't communicate with gnome keyring daemon via dbus: Failed to execute program gnome-keyring-daemon: Success

And when trying to edit a password in an account :

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 647, in <lambda>
    mi.connect("activate", lambda w, a: self.accounts.show_properties_dialog(a), acct)
  File "/usr/lib/python2.6/dist-packages/gwibber/configui.py", line 58, in show_properties_dialog
    else: acct.bind(w, widget)
  File "/usr/lib/python2.6/dist-packages/gwibber/config.py", line 90, in bind
    return Wrapper.bind(self, widget, "%s/%s" % (self.id, key), **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/config.py", line 42, in bind
    gwp.create_persistency_link(widget, "%s/%s" % (self.path, key), **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/swp.py", line 194, in __call__
    return handler(widget, *args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/gwibber/gwp.py", line 382, in _persistency_link_entry
    return PersistencyLink(entry, entry.get_text, entry.set_text, "changed", GConfValue(key, data_spec, *args, **kwargs))
  File "/usr/lib/python2.6/dist-packages/gwibber/swp.py", line 81, in __init__
    self.sync_widget()
  File "/usr/lib/python2.6/dist-packages/gwibber/swp.py", line 136, in sync_widget
    val = self.storage.data
  File "/usr/lib/python2.6/dist-packages/gwibber/gwp.py", line 144, in get_data
    gnomekeyring.ITEM_GENERIC_SECRET, {"id": self.key})[0].secret
gnomekeyring.NoKeyringDaemonError

[Andy Barilla (andybarilla)]

I did a fresh install of Arch Linux with Gnome 2.26 and this same error occurred. It appears that it gnome-keyring-daemon doesn't start correctly in Gnome 2.26 and this might now be distro specific.

[Addisu Z. Taddese (azeey)]

I just upgraded to Jaunty and have the same issue. I ran the gnome-keyring-daemon process as a foreground process and tried to change my twitter password setting in gwibber. The daemon aborted with:
gnome-keyring-daemon: egg-secure-memory.c:324: sec_check_guards: Assertion `((void**)cell->words)[cell->n_words - 1] == (void*)cell' failed.
Aborted (core dumped).

However, the NoKeyringDaemonError happened even when I wasn't trying to change my password. I just did the above test to see where the problem was. In any case, gwibber worked once I killed and restarted the gnome-keyring-daemon.

[Alexander Sack (asac)]

setting upstreamed bugs to "Triaged"

[Omer Akram (om26er)]

There have been many changes to gwibber since this bug was reported can any one using the development release or at minimum gwibber 2.0 please confirm if this is still an issue.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".