gm-notify crashed with GError in labelClick(): Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist

[Matthias Gehre]

After upgrading to oneiric beta, any click on the "Inbox" in the gm-notify indicator menu
crashes instead of launching firefox.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gm-notify 0.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Fri Sep 2 15:08:46 2011
ExecutablePath: /usr/bin/gm-notify
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gm-notify
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/zsh
PythonArgs: ['/usr/bin/gm-notify']
SourcePackage: gm-notify
Title: gm-notify crashed with GError in labelClick(): Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/gm-notify", line 199, in labelClick
     if self.client.get_bool("/apps/gm-notify/openclient"):
 GError: Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

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 #831491, 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.