Comment 6 for bug 442362

Revision history for this message
Nick Hlavacek (nick-nickspace) wrote :

I'm encountering this problem as well. Alarm is set for 05:45 and went off one hour early at 04:45. If I set an alarm for 5 minutes into the future and the date is scheduled for the alarm to happen every day then it will show that it is 23 hours and 5 minutes away from going off. If I set an alarm for 5 minutes into the future for the current date only the alarm will not add (as it would go off in the past).

If the bug is the problem with g_time_val_to_iso8601 and g_time_val_from_iso8601 then perhaps it would be useful to run a simple test when processing alarms. Write a time value to a file with g_time_val_to_iso8601 and then read it right back with g_time_val_from_iso8601. If the two values don't match, then add an hour to the time returned by g_time_val_from_iso8601. I haven't looked at the code so I don't know if this could work or not. Just a thought.

Kernel:
2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:00:22 UTC 2009