Re: [Evolution] CORBA error with evo-1.3 and 1.4

[Mark Gordon <mtgordon ximian com>]

Shifting from the previous thread to this one.

On Tue, 2003-05-20 at 16:17, Mike Godfrey wrote:
> Good day, eh.
>
> I'm running redhat 9; I just installed red-carpet and subscribed to the
> RH9, red carpet, and evo-beta channels.
>
> I tried running evo-1.3 and 1.4, but I got the following fatal error. 
> Anyone know what's wrong here?  I get a similar error message when
> running nautilus so I'm guessing it's a GNOME-2 thing (nautilus will run
> after complaining, but evo-1.3/1.4 will not).

It may be a problem with your Red Hat 9 install.  More speculation
follows.

> (I know what CORBA is, but I don't know what I'm supposed to to start
> the server up.)

Things are supposed to start automatically when you run evolution-1.3,
if they're not running already.  It shouldn't require any manually
starting of servers, nothing in /etc/init.d if that's what you're
thinking.

> Here is the message:
>
>
> > (evolution-1.3:24590): camel-WARNING **: could not load cert
> > /home/migod/.camel_certs/ab:05:41:71:58:a4:c1:ba:21:88:8d:ab:fd:35:69:72:
> > No such file or directory

One wonders why it would be looking for such a file and not finding it. 
Is this a case of copying ~/evolution from another machine or another
directory?

> > warning: failed to load external entity
> > "/home/migod/evolution/config/storage-set-view-expanded:default"

I suspect this is harmless.
 
> > (evolution-1.3:24590): evolution-shell-CRITICAL **: file e-storage-set.c:
> > line 639 (e_storage_set_get_folder): assertion `g_path_is_absolute (path)'
> > failed

This looks a bit more problematic, though I'm unable to reproduce, and
I'm not sure what it implies.

> > gtkhtml-ERROR **: gconf error: Configuration server couldn't be contacted:
> >  CORBA error: IDL:omg.org/CORBA/BAD_OPERATION:1.0

This suggests GConf problems.  This is Bad, since Evolution uses GConf
to store many of its settings.  If gconfd-2 isn't running, and won't
start (i.e. crashes on launch), this would pose problems for Evolution,
Nautilus, etc.  That's my guess as to the crux of the problem.

> >  aborting...

Suggesting that this is the fatal error.

> >  (evolution-1.3:24590): camel-WARNING **: could not load cert
> >  /home/migod/.camel_certs/ab:05:41:71:58:a4:c1:ba:21:88:8d:ab:fd:35:69:72:
> >  No such file or directory

Similar to the previous such error.

Debugging suggestion: try running /usr/libexec/gconfd-2 and see what it
says.  My guess is that it will complain, and the error message(s) might
be useful.

-Mark Gordon