And here is a very small patch for one of the Xlib crashes.
apply this patch from the topdir of multisync like this:
patch -p0 < <path to>/evolution_ecal.patch
Standard disclaimers apply like "make a backup first" :)
in the function evo2_calendar_modify when the passed variable data is
null the function tries to delete the entry with uid from evo and
returns TRUE if it succeeded. If it does not succeed the function goes
on and assumes there is valid information in data. This will of course
fail and make multisync fail.
So if data is null and the deletion fails we should return FALSE to
signal failed deletion.
Ron
--- ../multisync/plugins/evolution2_sync/src/evolution_ecal.c 2004-11-26 14:04:49.000000000 +0100
+++ plugins/evolution2_sync/src/evolution_ecal.c 2004-11-30 08:56:18.694375840 +0100
@@ -43,6 +43,11 @@
if (!data) {
if (e_cal_remove_object(env->calendar, uid, NULL))
return TRUE;
+ else
+ return FALSE; // we don't have data, so we might
+ // as well return as we cannot
+ // do anything with it
+ // [EMAIL PROTECTED]
}
//Remove BEGIN:VCALENDAR
