Re: gconf errors

[Havoc Pennington <hp redhat com>]

Hi,

I already followed up on gnome-devel-list, but for people on this list
who missed it, these are not really worth worrying about.

We need a way to tell gconfd at runtime which levels of logging to use
in gconf_log(), so we can turn off pretty much all logging by default
but still make it easy for people to flip on logging to diagnose
problems.

Havoc


Louis Garcia <louisg00 bellsouth net> writes:
> I'm seeing some errors from gconf and I don't know if there normal or their is
> something wrong:
> >starting (version 1.0.0), pid 739 user 'louisg'
> >No configuration files found, trying to use the default config source
> `xml:readwrite:/home/louisg/.gconf'
> >Initializing XML backend module
> >Removing stale lock `/home/louisg/.gconf/%gconf-xml-backend.lock' because of
> error pinging server: IDL:CORBA/COMM_FAILURE:1.0
> >Directory/file permissions for XML source at root /home/louisg/.gconf are:
> 700/600
> >Failed to notify listener 3875536900, removing: IDL:CORBA/COMM_FAILURE:1.0
> >Failed to notify listener 3841982466, removing: IDL:CORBA/COMM_FAILURE:1.0
> >15 items remain in the cache after cleaning already-synced items older than
> 300 seconds
> nautilus and evolution seem to be working fine.