Bug 305518 - Multiple suspended reminders don't retrigger at the right time
Summary: Multiple suspended reminders don't retrigger at the right time
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korgac
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-20 21:31 UTC by Martin Doucha
Modified: 2017-01-07 22:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Doucha 2012-08-20 21:31:19 UTC
When you suspend two reminders at a time, reminder A by an hour and reminder B a moment later by 5 minutes, reminder B will retrigger after an hour instead. This happens in both KDE 4.8.4 and 4.9.0.

Reproducible: Always
Comment 1 David Jarvie 2012-08-26 00:02:27 UTC
I can't reproduce this. Please say what version of KAlarm in KDE 4.9.0 you have seen this on (use Help -> About).

Can you please attach your KAlarm config file (~/.kde/share/config/kalarmrc or similar directory), and also an example calendar file copied BEFORE the alarms trigger and are suspended (probably ~/.kde/share/apps/kalarm/calendar.ics - if you have other alarms in the calendar, please specify which are the two which will be used to show the fault).
Comment 2 Martin Doucha 2012-08-26 09:03:36 UTC
Oops, sorry, I think this bugreport belongs to the korgac team. I thought KAlarm was handling all reminders on KDE4 including those set up in KOrganizer but apparently KOrganizer has its own reminder demon.
Comment 3 Denis Kurz 2016-09-24 21:04:24 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korgac (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:14:30 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.