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
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gm-notify (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I tried to start the program and this error came up.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gm-notify 0.10.3-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Sun Jul 31 00:50:09 2011
ExecutablePath: /usr/bin/gm-notify
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/gm-notify
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
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.
Traceback:
Traceback (most recent call last):
File "/usr/bin/
if self.client.
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 (12 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare tape vboxusers video
| 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 #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.