Re: Settings not saved with gconf 2.6.0

On Wed, 2004-07-07 at 08:58, Robin Holt wrote:
> I tried gconf-sanity-check-1 script which reported nothing.
> There doesn't appear to be a gconf-sanity-check-2 script
> anywhere.  This is a Fedora Core 2 install.

Try /usr/libexec/gconf-sanity-check-2

> I hoping for some guidance on how to get enough debugging
> information out of gconfd to tell me definitively that it
> my problems are due to the rpc.lockd/rpc.statd description
> on http://www.gnome.org/projects/gconf/ about the lock file
> problem. 

strace would show the problem (fcntl() returning EAGAIN or something)

>  Will the syslog messages indicate a lock file
> problem?  If so, what basic keywords should I be looking for
> in the log?

I'm not sure if it gets logged anymore.

> I have tried the lock file bypass description as well.  That
> doesn't seem to work.  I created an /etc/profile.d/gconf.sh
> script and put that into it.  The environment variable is set
> according to /proc/<pid>/environ, but there don't appear to
> be any files created in /tmp.  Was this method deprecated in
> later versions of gconfd?

The /tmp lock should be the default in FC2 in fact, IIRC.

What are the symptoms of the problem you're seeing?

Havoc