Gnome-terminal error in xfce

[Ben Hall]

Hi John,

I'm not sure, but I'd bet that this has to do with Gnome's problematic gconfd 
file locking.  (This is especially noticeable with NFS mounted home dirs, but 
I've also seen it happen on stand-alone systems, sometimes because evolution 
crashed.)

The solution/workaround is to manually remove all lock files in ~/.gconfd.

There's more info here:  (This is a temporary page.)

http://neo.caslab.queensu.ca/~bhall/stupid_gconf.html

The short version:  Try rm -rf  ~/.gconf*/*lock* and then relaunch the Gnome 
Terminal.  If that fixes it, you may consider adding this to your login 
script.

For the record, this was the major motivation for me to use XFCE for the 
undergraduate labs at work.  I was going to use RH's stock Gnome 2.4, but I 
was seeing too much of this sort of behaviour.  My solution was to stick with 
XFCE, xterm and other non-Gnome apps whenever possible.

Cheers,

Ben



On 02/21/2004 06:44 am, John Shane wrote:
> When I start Gnome terminal in xfce I sometimes get the following error:
>
>
> Configuration server couldn't be contacted:
>  CORBA error: IDL:omg.org/CORBA/BAD_OPERATION:1.0
>
> It doesn't happen all the time, and I have not yet figured out the
> pattern that triggers it.  The same thing happens sometimes when I use
> Nautilus in xfce4. It happens when I'm connected to the office LAN with
> permanent internet connection and also happens sometimes when I'm using
> the laptop on its own off the network.  I have gnome-terminal set as the
> terminal in my main menu configuration.  Could it have anything to do
> with my xfce4 configuration?   John
> _______________________________________________
> Xfce mailing list
> Xfce at xfce.org
> http://lunar-linux.org/mailman/listinfo/xfce
> http://www.xfce.org