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) |
New
|
Undecided
|
Unassigned |
Bug Description
lunched Ubuntu Software Center and then got the gwibber-service crash
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-6-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Jul 23 15:41:43 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
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-19 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
gwibber.log:
2011-07-19 22:33:57,103 - Gwibber Service - INFO - Running from the system path
2011-07-19 22:35:11,178 - Identi.ca - INFO - Cleaning up database...
2011-07-23 15:26:32,070 - Gwibber Service - INFO - Running from the system path
2011-07-23 15:27:43,278 - Identi.ca - INFO - Cleaning up database...
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.