Re: [Evolution] "Evolution can not start" dialog

[guenther <guenther rudersport de>]

On Mon, 2006-05-29 at 14:42 +0930, Iain Buchanan wrote:
> On Mon, 2006-05-29 at 02:39 +0200, guenther wrote: 
[...]
> > Generally you get this message, after updating Evo or building to a
> > different prefix, and starting that one -- with the the old b-a-s still
> > running. The issue is, that the running b-a-s does not find the
> > correct .server files in the dir where it expects them.
>
> But the problem comes and goes - one minute it works, and the next
> minute I can't start evolution. I _don't_ recompile anything, I _don't_
> have different versions of e-d-s or b-a-s or evo or anything lying
> around...
>
> Hence I don't understand your "after updating Evo or building"
> statement.

Yeah... This *used* to be an issue only in the case I outlined. Turns
out there is an unrelated b-a-s issue, that results in the very same
behavior and error message.

Really doesn't make my support on IRC and mailing lists any easier.
*sigh*


[...]
> > > I'll check out playing with mail-notification next, but at the moment, I
> > > can't reproduce the error...

There are hints in bugzilla that this actually may be related to m-n.
(FWIW, m-n 3.0 RC2 is out. Don't know if it addresses this issue, but I
am going to poke the author right now. :)


> > If it is the same prefix (likely, since you now cannot reproduce this
> > any more), this issue should be resolved by restarting b-a-s in whatever
> > way. Yes, rebooting (ugh) does this, too. ;-)
>
> OK, I couldn't reproduce it _then_ but it is still reproducible, when
> it decides to be.
>
> These are the only env vars that differ between "working" and "not
> working".  All of them seem to be unrelated.
[...]
> This is what I do to see the behaviour:
> open evolution (works)
> close evolution
> wait, without doing anything (don't know for how long)
> open evolution - "can't open" message
> log off, log on.
> open evolution (works again).
>
> I can do this over and over, without changing / compiling / installing anything.
>
> any comments?

See your own follow up. ;-)

FWIW, this does not seem to be a general issue. I have been running
GNOME 2.14.x and m-n for quite some time, and never had that issue
myself. Maybe I am just not using the part of m-n that triggers this,
though, didn't have a close look myself yet...

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