Daniel mailed me a copy of his calendar and I'm seeing the same behavior.
The interesting issue is that it's not happening for events created in the clock or calendar apps -- just the ones imported from Google calendar.
I suspect it's an issue with how indicator-datetime is handling the timezone strings there. A sample tzid:
DTSTART;TZID=/freeassociation.sourceforge.net/Tzfile/Europe/Berlin: 20150722T203000
Daniel mailed me a copy of his calendar and I'm seeing the same behavior.
The interesting issue is that it's not happening for events created in the clock or calendar apps -- just the ones imported from Google calendar.
I suspect it's an issue with how indicator-datetime is handling the timezone strings there. A sample tzid:
DTSTART; TZID=/freeassoc iation. sourceforge. net/Tzfile/ Europe/ Berlin:
20150722T203000