|Summary:||recurring alarms sometimes don't fire when they're supposed to|
|Product:||[Applications] kalarm||Reporter:||Andrew Schulman <andrex>|
|Component:||kalarmd||Assignee:||David Jarvie <djarvie>|
|Latest Commit:||Version Fixed In:|
screenshot of alarm schedule
M-F alarm fired on Saturday
Description Andrew Schulman 2007-06-19 12:18:07 UTC
Version: (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages OS: Linux I have an alarm set to recur every Mon-Fri at 9 AM. Sometimes it goes on time, and other times it waits for 1, 2, or 3 days, then fires. You can see this alarm at the top of the list in the screenshot, which I took this morning. Note that the alarm is scheduled to run next on 6/18 at 9 AM. But today is 6/19, and my host has been up continuously, with me logged in, for weeks. It should have fired yesterday morning, but it didn't. Any help would be much appreciated. Thanks, Andrew.
Comment 3 Andrew Schulman 2007-06-19 12:19:22 UTC
Created attachment 20904 [details] screenshot of alarm schedule
Comment 4 David Jarvie 2007-07-03 17:57:29 UTC
Is that the only alarm which is missed? I notice that you have another alarm scheduled weekly (a display alarm, on two days per week, shown second from the top in your screen dump) - does that ever fail to appear?
Comment 5 Andrew Schulman 2007-07-10 12:15:27 UTC
> Is that the only alarm which is missed? I notice that you > have another alarm scheduled weekly (a display alarm, on two days per > week, shown second from the top in your screen dump) - does that ever > fail to appear? I believe it's the only one that fails to run. The 2/week alarm does appear, I think on schedule, but to be honest I haven't paid close attention to it. I'll start tracking it more closely.
Comment 6 Andrew Schulman 2007-07-10 12:15:54 UTC
Created attachment 21111 [details] M-F alarm fired on Saturday FYI, here's one more screenshot. The highlighted message was sent on Saturday, July 7. But the alarm schedule is M-F.
Comment 7 David Jarvie 2007-08-01 19:59:31 UTC
The reason that the alarm is not triggering correctly is that exception dates are not handled properly. In the interim, until the bug is fixed, it should work if you remove the exceptions (and avoid using them in other alarms).
Comment 8 David Jarvie 2007-08-06 01:32:38 UTC
Fixed by SVN commits 696819 (trunk) and 696820 (KDE 3.5). The fix will be available in KDE 3.5.8 (if it is ever issued), and also in version 1.4.14 which will should be available soon from the KAlarm website.
Comment 9 Andrew Schulman 2007-08-06 15:27:36 UTC
I confirm the workaround. I removed the exception dates (which I had completely forgotten were in there-- I wonder if past exception dates should be automatically purged after some amount of time?) and the alarm now is running on schedule again. Thanks, Andrew.
Comment 10 David Jarvie 2007-08-06 17:31:10 UTC
There should be no need to purge exception dates once the fixed version is available. I doubt whether there would be demand for an option to automatically purge exception dates, so I'll leave it up to the user to purge them manually if required.
Comment 11 Andrew Schulman 2007-08-06 17:40:50 UTC
> There should be no need to purge exception dates once the fixed version is available. I doubt whether there would be demand for an option to automatically purge exception dates, so I'll leave it up to the user to purge them manually if required. > No problem-- just wondering. Thanks for fixing this. Andrew.