| Summary: | reminder shows all recurring reminders even though only one shall trigger | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Martin Koller <martin> |
| Component: | reminder daemon (korgac) [CLOSED: Use Reminder Daemon product] | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | f.koester, johannes, kdenis, prozac, wulf.richartz |
| Priority: | NOR | ||
| Version First Reported In: | 4.13 Pre | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot of reminder dialog | ||
|
Description
Martin Koller
2014-03-28 06:18:27 UTC
Created attachment 85803 [details]
screenshot of reminder dialog
Does it happen every minute? If yes, then this looks like https://bugs.kde.org/show_bug.cgi?id=250729 This happened to me too, and always around the 1st of april. Happens for me too with korganizer-4.11.5. It displays a reminder for _all_ of my contact's birthdays, dispite their date. Started some days ago and is very annoying . same here: kOrganizer 4.12.3 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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. please have a look here: https://bugs.kde.org/show_bug.cgi?id=250729 and I opened a new bug report here: https://bugs.kde.org/show_bug.cgi?id=361242 Wulf, thanks for reporting back. There's a whole bunch of reports for broken reminders, and I should probably try to clean those separately. As of now, I have no idea whether this bug should remain open... I leave it as is for now, unless you'd suggest otherwise. Hi Denis, thanks for your reply. I have no idea too, it's your decision. 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. |