alarms are one hour off when clock has changed due to daylight savings

Thank you for your bug report.
Actually, Alarm Clock stores the UNIX timestamp for the alarm trigger which it generates with mktime(). I'll investigate further.

On the Monday after the most recent time change, I was counting on Alarm Clock to remind me to pick my daughter up from school as usual. I happened to hover the mouse over the taskbar icon, and the help-tip looking thing popped up and I noticed it was counting down to an an hour after the correct set time. I opened the edit window for that alarm and changed a number and changed it back to the same number, and closed out. Now the hovering timer showed the correct countdown time. Same behavior previously reported, but I wanted to bring it back to your attention, as I found it to be of greater than "Low" importance.

Great program otherwise.

Good news, everyone! This bug has been fixed in rev 211.

This is still happening in 3.2 on Ubuntu 11.10. Any ideas when a fix will be available?

On Sun, Nov 6, 2011 at 16:18, Mannex <email address hidden> wrote:
> This is still happening in 3.2 on Ubuntu 11.10. Any ideas when a fix
> will be available?

A fix has been available in trunk for quite some time[1], but a
release has not yet been made with the fix. It will be included in the
next release, of which there is no ETA unfortunately.

[1] http://bazaar.launchpad.net/~joh/alarm-clock/trunk/revision/211

I was notified of my 10:30 am meeting at 11:30 am this morning.

I appreciate this has been fixed in trunk and committed. This clarification is for troubleshooting any future similar trouble in this or similar code; similar bugs will only occur twice a year so will be less "visible" than normal bugs. This is purely for reference in case this needs to be revisited, or for someone with a similar problem that could be pointed towards the patch for code re-use.
LTS users will have to use the workaround below for a some time (sorry about the pun)

After a few minutes testing this morning, (clocks changed to 1 hour ahead for summer) the alarms made before the timezone change were 1 hour late, even after logout/login cycle and then a planned reboot.

Workaround is to delete all alarms and remake them manually. Similarly, when timezone changes back, all alarms will be off-by-one-hour until deleted and remade again.

(thanks for useful prog btw)

  affects ubuntu/precise/alarm-clock-applet
  status confirmed
  subscribe ubuntu-sru

--
Kind regards,
Loong Jin

This bug is missing information detailed in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for it to comply with Stable Release Updates process. Please add a test case for recreating and the regression potential. Once this information is added to all the bugs addressed by the package in -proposed we will approve the upload. Thanks!

I've rejected this from the precise-proposed queue; changing the debhelper compat level is not a minimal change, and is not appropriate for an SRU.

The rest of the changes look good, however. Feel free to re-upload a package without that change (and update the bug with a test-case and regression potential/where-to-look-for-regressions section).

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release