Re: Error Messages

[Darin Adler <darin eazel com>]

on 5/4/01 8:01 AM, Pete Brayman at pete v-fib net wrote:

> After upgrading to the new Ximian
> 
> In my syslog I noticed this:
> May  3 09:16:07 lappy gconfd (pete-379): Failed to notify listener 2399142644,
> removing: IDL:CORBA/COMM_FAILURE:1.0
> May  3 09:16:07 lappy gconfd (pete-379): Failed to notify listener 2365588225,
> removing: IDL:CORBA/COMM_FAILURE:1.0
> May  3 09:16:07 lappy gconfd (pete-379): Failed to notify listener 2432697089,
> removing: IDL:CORBA/COMM_FAILURE:1.0
> May  3 09:16:08 lappy gconfd (pete-379): Failed to notify listener 2466251458,
> removing: IDL:CORBA/COMM_FAILURE:1.0
> May  3 09:16:09 lappy gconfd (pete-379): Failed to notify listener 2533360330,
> removing: IDL:CORBA/COMM_FAILURE:1.0
> 
> And these messages just continue, I have about a 40 page syslog of them for
> just yesterday.
> How can I either
> 
> A) fix this
> B) redirect the logging to someplace else so it's not plugging up my syslog

This bug is the known problem with Nautilus 1.0 - 1.0.2, fixed in HEAD and
the upcoming Nautilus 1.0.3. The huge number of log entries is unfortunate,
since this is actually part of normal operation of GConf, but a more serious
problem is that Nautilus is constantly being restarted by the session
manager, and this chews up a lot of CPU power.

While waiting for the 1.0.3 upgrade to come out, you can avoid the problem
by not invoking Nautilus from the command line, and using the "New Window"
command from the desktop's right-click menu instead.

    -- Darin