gwibber-service crashed with GError in __getitem__(): Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: GetIOR failed: The connection is closed)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gwibber
I believe the crash was triggered by the command below:
$ gconftool --recursive-unset /apps/panel && killall gnome-panel
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber-service 2.91.91-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf504
CheckboxSystem: b633b4f40868d49
Date: Fri Mar 11 21:42:17 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-service crashed with GError in __getitem__(): Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://
UpgradeStatus: Upgraded to natty on 2010-11-25 (106 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Alex Mayorga (alex-mayorga) 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 #713559, 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.