Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Apr 2004 21:48:29 -0400
From:      Brian Gruber <lists@bgruber.isa-geek.com>
To:        Andrew Thomson <andrewjt@applecomm.net>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: gnome settings daemon failing to start
Message-ID:  <20040416014829.GA18227@bgruber.isa-geek.com>
In-Reply-To: <1081986993.76324.8.camel@itouch-1011.prv.au.itouchnet.net>
References:  <1081842754.94842.6.camel@itouch-1011.prv.au.itouchnet.net> <1081859913.95770.2.camel@shumai.marcuscom.com> <1081896653.11882.1.camel@itouch-1011.prv.au.itouchnet.net> <1081897083.839.69.camel@gyros> <1081909977.76324.1.camel@itouch-1011.prv.au.itouchnet.net> <1081919385.52419.14.camel@shumai.marcuscom.com> <1081986993.76324.8.camel@itouch-1011.prv.au.itouchnet.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 15, 2004 at 09:56:34AM +1000, Andrew Thomson wrote:
> On Wed, 2004-04-14 at 15:09, Joe Marcus Clarke wrote:
> > On Tue, 2004-04-13 at 22:32, Andrew Thomson wrote:
> > > On Wed, 2004-04-14 at 08:58, Joe Marcus Clarke wrote:
> > > > On Tue, 2004-04-13 at 18:50, Andrew Thomson wrote:
> > > > > On Tue, 2004-04-13 at 22:38, Joe Marcus Clarke wrote:
> > > > > > On Tue, 2004-04-13 at 03:52, Andrew Thomson wrote:
> > > > > > > Hi,
> > > > > > > 
> > > > > > > After my upgrade to 2.6, everything went smoothly except for when I
> > > > > > > startup, I get a little dialogue complaining that the "gnome settings
> > > > > > > daemon" could not be started and thefore I get dodgy icons on the
> > > > > > > desktop.
> > > > > > > 
> > > > > > > I have created a new user and tried starting gnome and it all comes up
> > > > > > > perfectly. So I assume I have something funny lying around in one of the
> > > > > > > gnome . directories.
> > > > > > > 
> > > > > > > I have tried removing some obvious ones but no luck yet...
> > > > > > > 
> > > > > > > .esd_auth
> > > > > > > .gconf
> > > > > > > .gconfd
> > > > > > > .gnome
> > > > > > > .gnome2
> > > > > > > .gnome2_private
> > > > > > > .metacity
> > > > > > > .nautilus
> > > > > > > 
> > > > > > > Any clues on what's causing this problem?
> > > > > > 
> > > > > > You should try launching /usr/X11R6/libexec/gnome-settings-daemon by
> > > > > > hand to see exactly why it's not coming up.
> > > > > > 
> > > > > > Joe
> > > > > 
> > > > > Probably doesn't help much, but running the gnome-settings-daemon once
> > > > > everything has started results in a working gnome-settings-daemon!!
> > > > > 
> > > > > Restarted X again but still doesn't want to start on startup!
> > > > 
> > > > Okay, then what you need to do is start it manually, then save your
> > > > session, and log back in.
> > > > 
> > > 
> > > Sorry to be a pain,, no love after saving session and restarting..
> > > 
> > > Is this the normal output from gnome-settings-daemon ?
> > > 
> > > /usr/X11R6/libexec/gnome-settings-daemon
> > >                                                                                 ** (gnome-settings-daemon:76363): WARNING **: Unexpected error in waitpid() (No child processes)
> > >                                                                                 
> > > ** (gnome-settings-daemon:76363): WARNING **: Command xrdb -merge failed
> > >                                                                                 
> > > ** (gnome-settings-daemon:76363): WARNING **: Unexpected error in
> > > waitpid() (No child processes)
> > 
> > These messages are normal when I start g-s-d manually via a remote X
> > DISPLAY.  I don't know why it's not starting for you automatically. 
> > Perhaps it has something to do with your environment.  How do you start
> > GNOME?  What environment settings do you have?
> > 
> 
> Thanks for the assistance Joe.
> 
> Just start a gnome-session from my .xinitrc
> 
> However given everything works fine for other users I'll start tampering
> with my own account... I'll try and remove a few of the other
> directories Mezz suggested.

I had what sounds like the same problem when I first upgraded.  I
verified it was a settings problem at the time by making a new user,
who was able to log into gnome just fine.  I believe the magic thing
to do was wipe out my gconf settings.  This is a bit tricky though, as
you need to make sure that the gconfd stuff isn't running when you do
it.  There's probably a "right way," but I just made sure i had no
processes running with the exception of a shell and then deleted
"~/.gconf*".  I suppose that I had some setting or inconsistency in
gconf that the new gconf didn't like, though I never really figured
out what it was.

/brian


> 
> I'll keep the list posted on the outcome!
> 
> regards,
> 
> ajt.
> 
> _______________________________________________
> freebsd-gnome@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040416014829.GA18227>