Alarms 1 hour behind

[DebianSidUser]

I am using 1.2.4 and I set an alarm for 1PM and it woke me up at 12PM. (Yes my system clock is right)

[DebianSidUser (raza)]

Well it seems to be only a problem with that single alarm :/ I guess I'll just make another alarm

[DebianSidUser (raza)]

I was wrong, it's happening on all alarms. 1.2.4 ubuntu 9.10

[Christopher Berner (cberner)]

I'm having the same problem. It started happening to me after I upgraded to Ubuntu 9.10 and alarm-clock 1.2.4

[Phoenix Madrone (pellew)]

This appears to still be an issue in 1.2.5. Just upgraded to try to fix it, but all alarms are 1hr off still (including new ones.)

[sabby7890 (tsalacinski)]

This is still a work in progress. It seems there's a bug in GTK (?) - g_time_val_to_iso8601 converts the time value to iso8601 format (to save it in this format into the conf file), but g_time_val_from_iso8601 converts one hour behind. So converting time with this function and then converting it back is giving one hour delay. I am working on this, but unfortunately this will mean that configuration files will not be compatible with older versions.

[Nick Hlavacek (nick-nickspace)]

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

[zebul666 (zebul666)]

it's not gtk it's glib.
if you have a simple example that show the bad behavior of these functions. please post it. even better, report the bug to the glib devs. but only if you have strong evidence of that bug.

but for now, i think it's a problem in alarm-clock and not a problem with glib g_time_val_* functions.

[sabby7890 (tsalacinski)]

And I am SURE that it's a problem with these functions. Download this:

http://alarm-clock.pl/media/distfiles/alarm-clock-1.3-alpha.tar.bz2

This is a new version of AC without these functions in use (only scheduled alarms doesn't work yet). And yes, this is glib not gtk - but these are so dependant on each other that I just call everything gtk.

The configuration files used by this version will unfortunately be incompatible with previous versions.

[DebianSidUser (raza)]

I think I am going stay with Alarm Clock 0.9.19 until all the bugs are fixed, its the only version where everything functions and it also has AM/PM.

[sabby7890 (tsalacinski)]

Finally, fixed. Please retest.

[Monkey (monkey-libre)]

I´ve assigned this bug to the alarm-clock package. Anyone still has this problem?

Thank You for making Ubuntu better.