Comment 4 for bug 1390992

I'm seeing similar results.

Using a Nexus 4 running devel-proposed r28, I created a daily alarm to kick at 7:30 AM. (I'm in -6)

After I hit "save", the alarm showed up in clock-app for 12:28 AM and in indicator-datetime as 11:59 PM.

The tasks.ics created by this reads:

> BEGIN:VCALENDAR
> CALSCALE:GREGORIAN
> PRODID:-//Ximian//NONSGML Evolution Calendar//EN
> VERSION:2.0
> X-EVOLUTION-DATA-REVISION:2014-11-20T19:21:55.008187Z(6)
> BEGIN:VTODO
> UID:20141120T192155Z-3487-32011-1530-9@ubuntu-phablet
> DTSTAMP:20141120T192155Z
> DTSTART:19691231T235959
> DUE:19691231T235959
> RRULE:FREQ=DAILY
> SUMMARY:Alarm
> CATEGORIES:8��^A
> CREATED:20141120T192155Z
> LAST-MODIFIED:20141120T192155Z
> BEGIN:VALARM
> X-EVOLUTION-ALARM-UID:20141120T192155Z-3487-32011-1530-10@ubuntu-phablet
> ACTION:AUDIO
> ATTACH:file:///usr/share/sounds/ubuntu/ringtones/Suru arpeggio.ogg
> END:VALARM
> BEGIN:VALARM
> X-EVOLUTION-ALARM-UID:20141120T192155Z-3487-32011-1530-11@ubuntu-phablet
> ACTION:DISPLAY
> DESCRIPTION:Alarm
> END:VALARM
> END:VTODO
> END:VCALENDAR

* The CREATED and LAST-MODIFIED fields are correct in GMT

* The CATEGORIES field appears to be corrupt. Thinking out loud, maybe this is why i-datetime and clock-app give such different results?

* DTSTART and DUE of 19691231T235959: looks like a -1 status value is being used as a valid time_t somewhere.

* DTSTART and DUE are not needed for repeating VTODO items, although that's probably a topic for a separate ticket. (http://www.kanzaki.com/docs/ical/vtodo.html#descr)