Your message dated Sun, 26 Feb 2012 13:33:15 +
with message-id
and subject line Bug#648673: fixed in gconf 3.2.3-2
has caused the Debian Bug report #648673,
regarding gconf2: Add NEWS entry logout and -in needed after upgrade
to be marked as done.
This means that you claim that the problem
forcemerge 648673 648836
thanks
It's the same issue. After loggin out and back in gnome-terminal is
back again!
- Fabian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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
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
Oh hell... please ignore my last somewhat obsolete mail und blame
network-manager for it :D
greetings
Michael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
I can confirm a relogin or gconfd-2 kill (and so forced respawn) "fixes"
that problem. So it is rather a gnome principle as it seems. At least I
heard it numerous times a gnome-foo upgrade plus reboot or relogin is a
must.
I suggest to reduce the severity to minor. Maybe adding a sentence
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
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 à 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.GC
Le Mon, 14 Nov 2011 10:05:53 +0100,
Gergely Nagy 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 to the Orbit ->
> 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
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 oth
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:
Package: gconf2
Version: 3.2.3-1
Severity: grave
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"
doesn't exist
There d
14 matches
Mail list logo
