gwibber-service crashed with GError in __getitem__(): Falha ao acessar o servidor de configuração, a causa mais comum é a falta de configuração ou desconfiguração da sessão D-BUs para troca de informações. Acesse http://projects.gnome.org/gconf/ para mais informações (Detalhes - 1: GetIOR falhou: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus))
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gwibber
I was playing a DVD and gwiber crashed. I was connected in a wi-fi connection
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber-service 2.91.92-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Thu Mar 31 22:27:27 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=pt_BR:en
LANG=pt_BR.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-service crashed with GError in __getitem__(): Falha ao acessar o servidor de configuração, a causa mais comum é a falta de configuração ou desconfiguração da sessão D-BUs para troca de informações. Acesse http://
UpgradeStatus: Upgraded to natty on 2011-03-27 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| André Germano (ad-cg-06) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
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.