gwibber-service crashed with GError in __getitem__(): No se pudo contactar con el servidor de configuración: Error de D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Bug #851764 reported by psamuel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

problemas con gwibber al iniciar la sesion

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 16 06:00:52 2011
ExecutablePath: /usr/bin/gwibber-service
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=es_VE:es
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
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: Error de D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/gwibber/microblog/dispatcher.py", line 790, 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: Error de D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
psamuel (persaudsamuel) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.