CORBA error: BAD_OPERATION when nautilus / mrproject starts

ct · n00b Joined: 22 Jul 2002 Posts: 29

When nautilus starts I get the following error:

damodred · Posted: Wed Sep 18, 2002 12:14 pm Post subject:

Hi,

I have exactly the same problem you have mentioned, all the other threads related to similar problems didn't help me to solve the problem!

A few weeks ago I installed my system totally new, before this I had a similar configuration and I had not this problem with nautilus, now with the reinstalled system and really similar configuration (enlightenment and nautilus as directory manager, without whole gnome emerged) I get this annoying error sometimes I start nautilus (other gnome tools produce the same error but only AFTER I got the error starting nautilus)! So I think it has something to do with Nautilus and the gconf system.

Hope anyone can help with this problem!

damodred

charlieg · Posted: Wed Sep 18, 2002 2:23 pm Post subject: Potential fix?

I had this problem too, but I just went through an "emerge -u world" and it has... gone away?

Also I might suggest "emerge gnome-terminal multi-gnome-terminal" as they are not automatically done with an emerge gnome.
_________________
Want Free games?
Free Gamer - open source games list & commentary

Open source web-enabled rich UI platform: Vexi

damodred · Posted: Fri Sep 20, 2002 1:08 pm Post subject:

Okay my problem with nautilus is solved!

I used evolution as mail client, after several reboots I could reproduce the error:
- start of enlightenment
- start of my I-net connection
- evolution
- nautilus
this gave me constant the errors mentioned above

But not starting evolution was the solution! I can start any application in any order, nautilus will never fail! Only when I start Nautilus after evolution I get these silly errors...

emerge gconf or emerge -C evolution + emerge evolution didn't help to solve this, so I emerged sylpheed-claw as e-mail client!
And after a few days I can say that I never got the above mentioned errors again...

It would be interesting what is going wrong with evolution, before my reinstall of the system I didn't get these strange errors with evolution...

bye,
damodred

ct · n00b Joined: 22 Jul 2002 Posts: 29

Gone. The error does not show anymore.

I cannot for sure tell what solved the problem, my best guess is that

paul138 · Guru Joined: 09 Aug 2002 Posts: 370 Location: Ottawa, ON

For me the solution was much more simple than rebuilding. Create a link from /usr/libexec/gconfd-2 in /usr/bin

Fixed. :roll:

_________________
Talk is cheap because supply always exceeds demand.

kappax · Posted: Mon Sep 23, 2002 10:00 pm Post subject: Re: Simple

paul138 · Guru Joined: 09 Aug 2002 Posts: 370 Location: Ottawa, ON

pilla · Posted: Mon Sep 30, 2002 1:21 am Post subject: Re: Simple++

Didn' t work for me, but this works

paul138 · Guru Joined: 09 Aug 2002 Posts: 370 Location: Ottawa, ON

The resolution via the bug report I filed was to exit X all together and run oaf-slay, edit the .xinitrc and change window managers.

I was because (in my case) I was running fluxbox and using Galeon (Gnome 1.x) which started gconfd-1. Then Gnome 2x apps would crash because they were using gconfd-1 instead of gconfd2.
_________________
Talk is cheap because supply always exceeds demand.

joycea · Posted: Mon Dec 16, 2002 12:38 pm Post subject:

You can continue using fluxbox, just start the gconfd-2 daemon before doing anything else (ie. in your xinitrc)

paul138 · Guru Joined: 09 Aug 2002 Posts: 370 Location: Ottawa, ON

Which would be fine except that gconfd will die if not used for a period of time. :wink:

_________________
Talk is cheap because supply always exceeds demand.

joycea · Posted: Mon Dec 16, 2002 4:20 pm Post subject:

Interesting... after starting gconfd-2 before evolution my comp has run fine all day with no error boxes. Before that I would get an error whenever I started evolution. After investigating though ps lists the gconf I started awhile ago as a zombie process. I don't know what's happened, maybe it's just my lucky day so far.

Do you think running gconfd-2 just before I run nautilus each time might be a more permanent solution?

crimson · Posted: Wed Feb 26, 2003 4:50 am Post subject:

My problem is very similar, if I run gnome-terminal before I run galeon, I'm ok. But if I run galeon before running gnome-terminal "CORBA ERROR, 1.0 blabla".

So what is a good fix for this? I don't want to have to kill gconfd-1 everytime I want to run a terminal, or I don't want to have to make sure I run terminal first everytime I want to use Galeon.