gnome-terminal error
 

when opening gnome-terminal the computer give me the following error:

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

and the following detailed error:

Configuration server couldn't be contacted:
CORBA error: IDL:omg.org/CORBA/BAD_OPERATION:1.0
Configuration server couldn't be contacted:
CORBA error: IDL:omg.org/CORBA/BAD_OPERATION:1.0
Configuration server couldn't be contacted:
CORBA error: IDL:omg.org/CORBA/BAD_OPERATION:1.0


Not sure why I receive the error.


Could this have something to do with why only konqourer works and not nautilus? Just a thought. The terminal still works but gives the above error when started. The nautilus will start up after minutes. I have no problem starting other programs. In the past nautilus has worked fine for me.

For nautilus try

rm -rf ~/.nautilus

This will delete all nautilus configurations for your username

I'm not sure where gnome-terminal saves its settings. If you are really having problems you could

rm -rf ~/.gnome*

But this will delete all your gnome configurations. If your using the GNOME desktop you will have to change back all your preferences and changes that you have made.

I just used the rm -rf command on .gnome, .gnome2, .gnome_private, .gnome2_private, .nautilus, and .gconf.

The errors still appear. I am running fluxbox on a RH9 distro. The nautilus when trying to load will popup a gconf error dialog box that is empty, only has the title bar, and has a blank and unclosable window. A while later the nautilus will likeley appear. Still has not since I tried.

The gnome-terminal is comeing up with the same error. Is it possible the programs are trying to read from somewhere else on the drive.

The gnome-terminal has ceased to give me the error. I am still haveing problems with the nautilus. I don't get the g-conf error screen but it took nearly all night to load up....I woke up in the morning and it was loaded. Should I start a new thread for this problem?

Did you do something that caused the terminal error to stop?

Does nautilus come up quickly when in another user account or as root? Are you using the GNOME desktop or another desktop or window manager?