Re: All the icons disappeared from gnome panel / nautilus in unstable
- To: Adam C Powell IV <hazelsct@debian.org>
- Cc: debian-gtk-gnome@lists.debian.org
- Subject: Re: All the icons disappeared from gnome panel / nautilus in unstable
- From: Pasi Kärkkäinen <pasik@iki.fi>
- Date: Thu, 2 Feb 2006 18:22:10 +0200
- Message-id: <[🔎] 20060202162209.GB21866@edu.joroinen.fi>
- In-reply-to: <1138761359.13839.6.camel@doorstop.home.net>
- References: <1138287878.12468.21.camel@silicium.ccc.cea.fr> <20060126151431.GI28738@edu.joroinen.fi> <1138288822.12468.32.camel@silicium.ccc.cea.fr> <20060126153027.GJ28738@edu.joroinen.fi> <1138290070.12468.36.camel@silicium.ccc.cea.fr> <20060126154750.GK28738@edu.joroinen.fi> <20060126155632.GL28738@edu.joroinen.fi> <1138291281.12468.41.camel@silicium.ccc.cea.fr> <20060130194434.GZ28738@edu.joroinen.fi> <1138761359.13839.6.camel@doorstop.home.net>
On Tue, Jan 31, 2006 at 09:35:58PM -0500, Adam C Powell IV wrote:
> On Mon, 2006-01-30 at 21:44 +0200, Pasi Kärkkäinen wrote:
> > On Thu, Jan 26, 2006 at 05:01:21PM +0100, Josselin Mouette wrote:
> > > Le jeudi 26 janvier 2006 à 17:56 +0200, Pasi Kärkkäinen a écrit :
> > > > In fact I still seem to have some problems:
> > > >
> > > > $ gnome-keyboard-properties
> > > >
> > > > (gnome-keyboard-properties:6826): capplet-common-WARNING **: NULL GConf
> > > > value: /desktop/gnome/peripherals/keyboard/repeat: possibly incomplete setup
> > > >
> > > > (gnome-keyboard-properties:6826): capplet-common-WARNING **: NULL GConf
> > > > value: /desktop/gnome/typing_break/enabled: possibly incomplete setup
> > > >
> > > >
> > > > What other schemes should I register? I wonder why these are not registered
> > > > automatically..
> > >
> > > You'd better reinstall libgnome2-common entirely...
> >
> > That fixed the problems.. Thanks!
>
> Thanks, that fixed the identical problem for me which appeared on an
> upgrade last week from sarge to etch (2.10). One machine had this
> problem, two others didn't.
>
> Could it be that the order of package installation or configuration
> sometimes leads to this issue? This sounds like an important bug...
>
> -Adam
Yes.. I also had this problem only in 1/3 computers :)
-- Pasi
Reply to: