On Fri, 2009-11-06 at 22:52 +0000, John Dykstra wrote: > [2009-11-06 15:16:55.186] calendar: could not encode item as iCal: > 040000008200E00074C5B7101A82E00800000000308FEABFA05DC801000000000000000010000000F0D61F794250FC45A6D673BD47934D15-rid > > I've tried doing the same thing on a different machine where the > Evolution calendar is empty except for a test entry, and things seem to > work fine. So this might well be a corrupted entry in the first > machine's default calendar, but the hex string in the error message > doesn't help me to find it.
The part before "-rid" should be the value of a UID property in that default calendar. Have a look at the output of "syncevolution", it'll tell you the path to the .ics file with the calendar data. Make sure Evolution is not running (evolution --force-shutdown). Then check that file, search for 040000008200... and remove the VEVENT which contains it. Keep a copy, just in case. One reason for this kind of failure is a VEVENT which refers to a VTIMEZONE (via TZID) which is not available. The .ics file is corrupt in such a case. There was a user with this problem before; we were uncertain how to handle this and thus don't have a workaround in SyncEvolution. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
