retitle 648673 gconf2: Add NEWS entry logout and -in needed after upgrade
quit
Am Montag, den 14.11.2011, 16:39 +0100 schrieb Vincent Lefevre:
On 2011-11-14 15:27:04 +0100, Josselin Mouette wrote:
Have you tried logging out and in again? The upgrade cannot,
unfortunately, be conducted in a
Processing commands for cont...@bugs.debian.org:
retitle 648673 gconf2: Add NEWS entry logout and -in needed after upgrade
Bug #648673 [gconf2] GConf Error in Emacs, Liferea, Evolution and others (D-BUS
error)
Changed Bug title to 'gconf2: Add NEWS entry logout and -in needed after
upgrade
retitle 648673 GConf Error in Emacs, Liferea, Evolution and others (D-BUS error)
quit
Am Montag, den 14.11.2011, 00:30 +0100 schrieb Vincent Lefevre:
Package: gconf2
Version: 3.2.3-1
Severity: grave
After the gconf2 upgrade, I get the following error when I run Emacs:
GConf Error:
Processing commands for cont...@bugs.debian.org:
retitle 648673 GConf Error in Emacs, Liferea, Evolution and others (D-BUS
error)
Bug #648673 [gconf2] gconf2: GConf Error in Emacs and Liferea (D-BUS error)
Changed Bug title to 'GConf Error in Emacs, Liferea, Evolution and others
(D-BUS error
Evolution does not find its configuration data either and throws error
messages and starts with the new configuration dialog.
(evolution:9622): evolution-shell-WARNING **: Der
Konfigurationsserver konnte nicht kontaktiert werden: D-BUS-Fehler: Method
GetDefaultDatabase with
Le Mon, 14 Nov 2011 10:05:53 +0100,
Gergely Nagy alger...@balabit.hu a écrit :
I suppose, pretty much everything that touches gconf breaks in similar
ways.
An easy workaround seems to kill all the gconfd-2 (killall gconfd-2)
and let the daemon respawn automatically.
This is probably related
Le lundi 14 novembre 2011 à 09:34 +0100, Paul Menzel a écrit :
After the gconf2 upgrade, I get the following error when I run Emacs:
GConf Error: Configuration server couldn't be contacted: D-BUS error:
Method GetDefaultDatabase with signature on interface
org.gnome.GConf.Server
On 2011-11-14 15:27:04 +0100, Josselin Mouette wrote:
Have you tried logging out and in again? The upgrade cannot,
unfortunately, be conducted in a way that lets new applications in a
running session work correctly.
The problem disappears after logging out and in again.
This is the kind of
Le lundi 14 novembre 2011 à 16:39 +0100, Vincent Lefevre a écrit :
This is the kind of information that the user would like to know
(to avoid doing the upgrade at the wrong time and to know that these
kinds of errors are expected), possibly before upgrading. Perhaps
the NEWS file would be the
9 matches
Mail list logo
