gwibber-accounts crashed with IOError in __init__()

[skep]

Binary package hint: gwibber

.

ProblemType: Crash
Architecture: i386
Date: Mon Feb 22 16:54:31 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-accounts
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.29.90.1-0ubuntu1
PackageArchitecture: all
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/bin/python /usr/bin/gwibber-accounts
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
PythonArgs: ['/usr/bin/gwibber-accounts']
SourcePackage: gwibber
Title: gwibber-accounts crashed with IOError in __init__()
Uname: Linux 2.6.32-13-generic i686
UserGroups:

[Victor Vargas (kamus)]

What version of gwibber do you use? did you follow any special step to produce this crash? Thanks in advance

[skep (skep)]

gwibber version is: 2.29.90.1-0ubuntu1

I can reproduce the crash. It happens then I click on "Broadcast Accounts..." on the gnome panel...

[bp (badpazzword)]

Confirmed in 2.29.90.1-0ubuntu2 when launched from the Me menu ("Broascast accounts") in Ubuntu 10.04.

[bp (badpazzword)]

The crash no longer happens under the same configuration since I rebooted the system after applying the updates. Rebooting, indeed, was required for the Me menu update to come in effect.

[Matt Mossholder (matt-mossholder)]

This appears to happen when gnome-keyring-daemon doesn't start up correctly. In my case, I am using krb5 authentication, and the pam-gnome-keyring module doesn't startup the daemon properly. This might be a major problem for enterprise users. In my case, it also impacts Ubuntu One and Empathy, as they both store secrets in the keyring as well.

I'm using a fully patched (as of the moment) Lucid.

[Omer Akram (om26er)]

Can any one please facing this confirm if this is still an issue in gwibber 2.29.92

[TommyBoy (thomaslloyd)]

2.29.92.1 Seems to still have the same issue:

Console Output:

** (gwibber:2594): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:2594): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:2594): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 50, in <module>
    from gwibber import client
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 3, in <module>
    import gtk, gobject, gwui, util, resources, actions, json, gconf
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 2, in <module>
    import os, json, urlparse, resources, util
  File "/usr/lib/python2.6/dist-packages/gwibber/util.py", line 2, in <module>
    from microblog.util.couch import RecordMonitor
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/util/couch.py", line 4, in <module>
    import desktopcouch, pycurl, oauth, threading, urllib, re, json
  File "/usr/lib/python2.6/dist-packages/desktopcouch/__init__.py", line 20, in <module>
    from desktopcouch.start_local_couchdb import process_is_couchdb, read_pidfile
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 38, in <module>
    from desktopcouch import local_files
  File "/usr/lib/python2.6/dist-packages/desktopcouch/local_files.py", line 277, in <module>
    xdg_base_dirs.save_config_path("desktop-couch"))
  File "/usr/lib/python2.6/dist-packages/desktopcouch/local_files.py", line 231, in __init__
    self.configuration = _Configuration(self)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/local_files.py", line 90, in __init__
    {'desktopcouch': 'basic'})
gnomekeyring.IOError

[Oxymoron (dennispersson84)]

I get the same problem, but only in the UNR! Not in the normal ubuntu

[Victor Vargas (kamus)]

@skep, Please could you run under latest version of gwibber: gwibber --debug > gwibber-debug.log and attach output to your report (following your steps to reproduce this issue), Thanks!

[Victor Vargas (kamus)]

@skep, any news about this issue? is still affecting you? Thanks!

[skep (skep)]

@Kamus
Seems to work now, just tested it and no crash. All seems normal as it should now :)

[Victor Vargas (kamus)]

@skep, According to your last message this issue was solved after an upgrade of gwibber so for now I will close this report an mark as invalid but if you encounter that this issue reappear please reopened again. Thanks!