gwibber-service crashed with GError in __getitem__(): Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm running the following Gwibber versios:
gwibber 3.1.2-0ubuntu1
gwibber-service 3.1.2-0ubuntu1
I had fired up Gwibber and was looking to change some of the preference settings when I received this error. I'm currently running the alpha version of Oneric on this machine.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-5-generic i686
NonfreeKernelMo
Architecture: i386
Date: Sun Jul 17 22:23:18 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-service crashed with GError in __getitem__(): Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.
Traceback:
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
GError: Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.
UpgradeStatus: Upgraded to oneiric on 2011-07-14 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.