Re: Error Messages



Pete Brayman <pete v-fib net> writes:
> 
>  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
> 

The problem (we think) is that the session manager is constantly
respawning Nautilus.

One way to reproduce it is to type "nautilus" at the command line
while nautilus is already running. In this case, the nautilus program:
 - registers with the session manager to be respawned
 - asks existing nautilus to open a new nautilus window
 - exits

Then it gets respawned, over and over and over... 

The log messages are GConf noticing that each successive Nautilus has
disappeared.

The new Nautilus coming out on Monday is supposed to fix this.

You can probably fix it in the short term by logging out, and editing
~/.gnome/session to clean out the extra nautilus. Or you can maybe use
the "startup programs" capplet, but the problem I had there is that
when you pushed the "running programs" button often the extra Nautilus
wasn't running at that moment so it wasn't there to remove, or
something.

Havoc




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]