https://bugs.freedesktop.org/show_bug.cgi?id=91318
--- Comment #3 from Graham Cobb <g+syncevolution(a)cobb.uk.net> ---
Ignore last comment -- I was being stupid. I can reproduce it and now I have
added logging it turns out that this is a much more frequent problem than I had
realised (at least 10% of my events hit it). The result is that for events
which have this problem, the event local time (e.g. 16:00 India time) is
re-interpreted as though it were 16:00 UTC (because the VTIMEZONE is invalid
and is ignored).
I have a fix and am testing it.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.