By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 356 - Kontact displays alarms from previous day when first opened
Summary: Kontact displays alarms from previous day when first opened
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdepim (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency treegraph
 
Reported: 2010-10-08 09:39 CDT by John A. Sullivan III
Modified: 2018-08-30 02:52 CDT (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String: 3.5.12
Application Version: 1.2.9 Kontact / 3.5.9 KOrganizer
Application Name: Kontact / KOrganizer


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John A. Sullivan III 2010-10-08 09:39:22 CDT
Most days, (perhaps all but I've not been diligent enough to check), when I first start Kontact, I receive popup messages from KOrganizer about appointments from the previous day which were already acknowledged when they popped up on the previous day.
Comment 1 Darrell 2013-05-22 22:36:08 CDT
Is this report still valid?
Comment 2 deloptes 2017-05-02 06:34:17 CDT
I think this is default behavior of pim managers - at least all I have used - on phone or outlook, lotus notes do the same.

I suggest to mark it as wont fix (I can't do that)
Comment 3 Michele Calgaro 2018-07-27 10:36:14 CDT
If the appointment was already acknowledge, it should not show up again.
Comment 4 deloptes 2018-07-27 14:56:42 CDT
Indeed the only way you do "acknowledge" properly is to use "Dismiss Reminder" button.
I've been using it extensively for the past 10y, and I don't see an issue with it at all.

regards
Comment 5 Michele Calgaro 2018-07-28 02:45:56 CDT
Thanks Emanoil, your feedback is quite good.
We will review this bug in R14.1 series (I am currently preparing a list) and if we find no issue here, we will simply close the bug. If we find a problem, we will prepare a fix :-)