On Fri, 2006-05-26 at 09:06 +0930, Iain Buchanan wrote:
[...]
> > > I have no idea what this means or how to fix it.
> >
> > quoting harish:
> > "The message means what it says - The configuration is not what it
> > should be for the application to run well.
>
> what configuration? I don't understand it because I don't change any
> configuration between working and not-woring states.
>
> > The work-arounds suggested all refer to environments where multiple
> > versions of evolution/eds co-exist
>
> really? What work-arounds are you referring to? I couldn't see any
> mention of multiple versions, nor do I have multiple versions of evo or
> eds.
>
> > The action required towards a full solution is to get the environment to
> > a valid state - remove conflicting versions or isolating matched
> > versions in your shell environment through proper settings to
> > BONOBO_ACTIVATION_PATH, LD_LIBRARY_PATH etc.
> >
> > So this is not a 'bug' that can be fixed by modifying the code. What may
> > be a bug indeed is documentation (or a lack of it) on the prevention and
> > recovery of such errors."
>
> Unless it's evolution that is making the environment get in this state,
> or evolution being confused about it, when nothing is really wrong.
No, it is not Evo. :)
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.
Killing b-a-s often solves this issue already.
Changing the BONOBO_* env var mentioned previously is one way to solve
this, if simply kicking b-a-s does not do it (most likely, cause Evo and
friends have been built to a new prefix). The best fix though is, to
change the b-a-s config and make it aware of the new prefix.
> I checked my environment when evolution works (with set), and compared
> it to the environment when it doesn't work, and I don't see any
> differences.
>
> I'll check out playing with mail-notification next, but at the moment, I
> can't reproduce the error...
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. ;-)
> thanks for all the help :)
--
char *t="[EMAIL PROTECTED]";
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; }}}
_______________________________________________
Evolution-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-list
