| Summary: | pre, post actions repeated over 100 times when kalarm is restarted | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Charles Evans <cvevans> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Charles Evans
2007-04-10 19:08:07 UTC
Am I right in thinking that the alarms are set to have a daily type recurrence with a recurrence interval of more than one day? Are post actions ever executed without the alarm window having been displayed? Or is there also a problem with alarms being displayed even though they are too late and should have been cancelled? I've fixed one bug whereby the alarm daemon triggers the same alarm multiple times (SVN commit 653810). This will reduce, but not yet eliminate, multiple executions of pre-alarm actions. The bug concerning multiple execution of pre-alarm actions is now fixed (SVN commits 653990 and 653991). I haven't been able to reproduce multiple execution of POST-alarm actions. Can you please confirm that this does indeed happen (as opposed to PRE-alarm actions), and provide an example calendar file which demonstrates the problem. The calendar file is $KDEHOME/share/apps/kalarm/calendar.ics . Most alarms are daily with cancel if 1 day late. A few are every 3 or 4 hours. Post-alarm actions run dozens of times each if it is time for the alarm to be cancelled and re-issued. I think the actions do alarm on first restart. I think they run without a popup on additional restarts. I will try to pin this down next weekend. I have not checked out KDE source yet. Could you please provide a sample svn command to get kalarm anonymously? I will try to test a scaled-down calendar file next weekend, time permitting. Thanks for the quick action! I think that I may now have seen something of what you describe on login. It looks as if alarms displayed at logout are sometimes displayed so fleetingly at login that you don't see them, but they still execute the post-alarm action. The fix to prevent the alarm daemon triggering the same alarm multiple times should, I think, have helped reduce the number of multiple post-action executions as well as pre-actions. I'll investigate more, and with any luck will find a fix before next weekend. To obtain the latest official KDE 3.5 sources (including the latest fixes), use the command: svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdepim This downloads the whole of kdepim. You need to run 'make -f Makefile.cvs' first on the SVN sources before running ./configure. You have to build kdepim as a whole in order to build kalarm since it contains several libraries which kalarm needs - but once the kalarm module has built, you can cancel the rest of the build if you want. See http://techbase.kde.org/Getting_Started/Build/Stable_Version for more details. I've fixed another bug (bug 143891) which may have some impact on your problem. I can't see any further error, so it would be great if you could download the latest SVN sources and let me know if it now works correctly. I've now issued version 1.4.11 with the corrections on the KAlarm website (http://www.astrojar.org.uk/kalarm). It's easier to build that than to download and build kdepim from SVN. I will assume the bug is fixed in KDE 3.5.7 unless I hear to the contrary. |