| Summary: | "Any time" alarms repeat one per minute | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Andrew Schulman <andrex> |
| Component: | kalarmd | 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: | ||
| Sentry Crash Report: | |||
| Attachments: |
screenshot of scheduled task
screenshot 1 of my email inbox screenshot 2 of my email inbox kalarmrc kalarmdrc calendar.ics |
||
|
Description
Andrew Schulman
2007-06-19 11:59:09 UTC
Created attachment 20896 [details]
screenshot of scheduled task
Created attachment 20897 [details]
screenshot 1 of my email inbox
Created attachment 20898 [details]
screenshot 2 of my email inbox
Created attachment 20899 [details]
kalarmrc
Created attachment 20900 [details]
kalarmdrc
Created attachment 20901 [details]
calendar.ics
Using your config file and calendar entry, I don't see the fault occur on my system. I run a self-compiled KDE, but since I run Debian, I'll try running the Debian KDE packages and see what happens with them. Unfortunately I won't have a chance to work on KAlarm for the next couple of weeks, but I'll definitely look at it after that. I can't reproduce the fault on my system. Could you please try installing a debug Debian package of KAlarm 1.4.14, which you can download from http://www.astrojar.org.uk/linux/download/kalarm-debug_1.4.14-1_i386.deb. You'll need to use the --force-overwrite option to dpkg when you install it, since it overwrites the normal kalarm package. This version will output lots of debug messages if you start kalarmd and kalarm from a terminal. To set it up, first run kdebugdialog --fullmode Select each of the following items: 5900 (kalarmd), 5901 (kalarmd check), 5950 (kalarm). For each, set all output categories to "File" and enter a file name including the full path (setting each to the same file). This file will hold the debug output. Kill kalarm and kalarmd. Check to ensure that both have been successfully terminated, since one can start the other automatically if an alarm triggers. In a terminal window, run first kalarmd and then immediately afterwards kalarm, ensuring that no alarms are waiting to be triggered at the time (if they are, kalarmd might start kalarm automatically which will prevent kalarm outputting debug information). Once you have seen the fault occur, kill the kalarm and kalarmd to stop the debug output and start them normally again (i.e. not from a terminal window). Compress and submit the debug file, and indicate the date/time at which the fault started happening again. Note that the debug file will grow to a large size, so it's best to start the experiment shortly before you expect the fault to occur. Check afterwards to ensure that the debug file is not still being written to - if it is, run 'kdebugdialog --fullmode' again and set all the outputs to "Shell". Hopefully this might give me enough information to track down the fault. > I can't reproduce the fault on my system. Could you please
> try installing a debug Debian package of KAlarm 1.4.14, which you can
> download from
> http://www.astrojar.org.uk/linux/download/kalarm-debug_1.4.14-1_i386.deb
I'd be glad to do this, but I have an amd64 host. I tried installing the
above package with --force-architecture, but it wouldn't run.
If you can build the package for amd64, I'll be glad to use that.
Otherwise, I don't mind building it from source, if you'll tell me what
the proper switches are to build a debug version.
Thanks,
Andrew.
> > I can't reproduce the fault on my system. Could you please > > try installing a debug Debian package of KAlarm 1.4.14, which you can > > download from > > http://www.astrojar.org.uk/linux/download/kalarm-debug_1.4.14-1_i386.d > >eb > > I'd be glad to do this, but I have an amd64 host. I tried installing > the above package with --force-architecture, but it wouldn't run. > > If you can build the package for amd64, I'll be glad to use that. > Otherwise, I don't mind building it from source, if you'll tell me what > the proper switches are to build a debug version. Nevermind that for now-- I forgot that I have an i386 chroot. I installed it there and started kalarmd and kalarm per your instructions. I have a monthly alarm set to go tomorrow, so I'll see if the fault occurs then. If not I'll try moving the dates up on some of the other alarms that have shown the fault. When I have a log I'll get back to you. Andrew. As of now, I can't reproduce this bug. I tried using your debug version in my i386 chroot, but this had other problems, e.g. with mail delivery. So I uninstalled the i386 version and have gone back to running the standard kalarm package in my amd64 environment. I've tried changing the dates on some of the alarms that gave me trouble before, but they worked normally. I'm going to try this one more time: I reset the date of the alarm I originally reported on, to fire tomorrow. If it works normally, then I guess the bug has fixed itself. I'll let you know. Maybe the fix to bug 146953 also fixed this bug. Andrew. I finally managed to reproduce this bug while fixing another (where date-only alarms sometimes didn't trigger at all). Now fixed in KDE 3.5 and trunk (SVN commits 732115 and 732144). > Now fixed in KDE 3.5 and trunk (SVN commits 732115 and 732144).
Excellent, thank you. Andrew.
The fix is now available in version 1.4.18 which is available for download from http://www.astrojar.org.uk/kalarm (source, Debian testing and Slackware packages are available). It will also be available very soon in the next development version, 1.9.9beta. |