Re: Configuration server couldn't be contacted

[Dave Lawrence <dgl integrinautics com>]

I fixed my problem by removing the file ~/.gconfd/lock/ior
which looked like this:
31132:IOR:010000001500000049444c3a436f6e6669675365727665723a312e300000000001000000caaedfba5000000001010000270000002f746d702f6f726269742d64676c2f6f72622

d333537373632323137323130383539323834350000000000001800000000000000d3bcb17342bafae7010000007c4a1559951549f7

I don't know how to reproduce this problem, but I suspect it had
something to do with exiting Xwindows ungracefully (due to my
computer hanging) or having run X from two computers
simultaneously.

Thanks for your suggestions...

Cheers...

                     Dave

PS - Should this be added to bugzilla for nautilus or gconf or both or
neither??

> For the benefit of those who didn't read my earlier message, nautilus
> crashes
> after printing:
> Eel-WARNING **: GConf error:
>   Configuration server couldn't be contacted:
>  Adding client to server's list failed, CORBA error:
> IDL:omg.org/CORBA/COMM_FAIL
> URE:1.0
> (this is printed 244 times)
>
> Eel-WARNING **: GConf error:
>   Failed to launch configuration server: Failed to create pipe for
> communicating with child process (Too many open files)
> (this is printed 92 times)
>
> GnomeVFS-pthread-ERROR **: file gnome-vfs-job.c: line 598
> (gnome_vfs_job_set): assertion failed:
> (gnome_vfs_context_get_cancellation (op->context) != NULL)
> aborting...
> (this is printed once, followed by a core dump)
>