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

[guenther <guenther rudersport de>]

> 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. 

I would be really surprised, if 1.4 would not act exactly as 1.3:

[guenther monkey guenther]$ ls -la /usr/bin/evolution-1.*
-rwxr-xr-x    1 root     root      7540758 May  7 20:03 /usr/bin/evolution-1.3*
lrwxrwxrwx    1 root     root           22 May  9 02:48 /usr/bin/evolution-1.4 -> /usr/bin/evolution-1.3*

Evo 1.4 isn't released yet... ;-)


> 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).
>
> (I know what CORBA is, but I don't know what I'm supposed to to start
> the server up.)
>
>
> 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

Damn, I should not test everything on my production system... ;-)

Out of curiosity I just deleted my ~/.camel_certs/* files -- and I tell
you, they _are_, what I supposed: That are your SSL certificates -- I
assume, you use IMAPS like me...


The previous error messages might be some stale processes/files in your
/tmp directory. I deleted them (in fact I removed everything in /tmp
including hidden . files) and even rebooted. That doesn't fix the
problem for me (I did not get your previous error messages) but might be
good for you.

It seems, that rude method fixed another strange issue: I was prompted
with an update dialog. :-/ The steps above cured that. If you get bugged
with such message, just Cancel and do them.


After reboot Evo started again, but could not connect. It plainly tried
to contact port 143 (IMAP) and failed for sure.

Even while Evo still trying to connect IMAP, go to the Settings and
_disable_ all IMAPS accounts. Close Evo and run
# evolution-1.3 --force-shutdown

Now run Evo again, enable your IMAPS accounts, accept the certificates
and continue work... ;-)


FYI: You cannot convince Evo to use SSL without closing. Known bug:
http://bugzilla.ximian.com/show_bug.cgi?id=43215

...guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}