gwibber-service crashed with GError in __getitem__(): Не удалось подключиться к серверу конфигурации: 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
2
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.4+r1083-
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Tue Aug 2 03:08:41 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANG=ru_RU.UTF-8
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-service crashed with GError in __getitem__(): Не удалось подключиться к серверу конфигурации: 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: Не удалось подключиться к серверу конфигурации: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.
UpgradeStatus: Upgraded to oneiric on 2011-07-29 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
gwibber.log:
2011-08-02 02:38:29,663 - Gwibber Service - INFO - Running from the system path
2011-08-02 02:38:55,173 - Facebook - ERROR - Failed to raise client (DBusException(
2011-08-02 02:39:41,649 - Facebook - INFO - Cleaning up database...
2011-08-02 03:08:22,467 - Facebook - ERROR - Failed to raise client (DBusException(
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.