An error occurred while loading or saving configuration information for Nautilus. Some of your configuration settings may not work properly.

[manzur]

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)

[manzur (sl-solaris)]

i am using ubuntu 8.10

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * The error seems to be a gconf one rather, do you get such warning in other software

 This will help us to find and resolve the problem.

[manzur (sl-solaris)]

no, this is the first time

[Sebastien Bacher (seb128)]

closing the bug for now since that doesn't seem to be a nautilus was a one time bug and lacks detail to work on the bug, you can reopen if you get the issue again though

[ehendric (eric-hndrcks)]

I get the exact same errors. I had to do a hard shutdown on my Dell XPS M1530 once. When I powered it back on, I started getting those errors every time I start my system.

Please advise, thanks,

Eric

[Chuck Money (chuckdmoney)]

I also get this error every time I reboot Ubuntu 9.04. This error is still current and occurs on every boot. My theory is that the problem is exactly what it says it is - I probably killed power to the system, leaving a lock file somewhere. My question is simply where this lock file would be, so I can delete the lock file and reboot. Clearly if it ceases to display the error, then we know what it is and can fix it.

Until someone can tell me what lock file I should try to delete, I request that this big be reopened. I'll be happy to provide any information I can to track it down. I don't think it's relevant since it started later, but my GNOME Panel also fails to load the zeroconf (avahi) service discovery applet the last 2 times I've rebooted. The error this bug describes, on the other hand, has been occurring for a week wherein I have rebooted at least 5 times.

[Caglar Dursun (caglardursun)]

After I delete the file with the extension ".gedit" under /tmp folder.I got the same error.May be this information could be helpfull

[Matthew Busche (mtbusche)]

I had never seen this error before until I started the upgrade from Hardy Heron LTS to 10.04 LTS. This upgrade is actually still in progress, but during the upgrade I got a pop-up with this exact error message.

[Matthew Busche (mtbusche)]

Just an update: this was the content of the details section of that popup error:

Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0

[Sebastien Bacher (seb128)]

nautilus stopped using gconf which deprecates that issue