gwibber-service crashed with GError in __getitem__(): No se pudo contactar con el servidor de configuración: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist

[Hernan.]

error al crear una cuenta en gwibber

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.4+r1083-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Aug 2 12:50:28 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=es_VE:es
 LANG=es_VE.UTF-8
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with GError in __getitem__(): No se pudo contactar con el servidor de configuración: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/gwibber/microblog/dispatcher.py", line 777, in refresh
   File "/usr/lib/python2.7/dist-packages/gwibber/microblog/config.py", line 78, in __getitem__
   File "/usr/lib/python2.7/dist-packages/gwibber/microblog/config.py", line 47, in __getitem__
 GError: No se pudo contactar con el servidor de configuración: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist
UpgradeStatus: Upgraded to oneiric on 2011-07-29 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #619654, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.