Bug 514500 - After the 6.6.1 (25.12.1-1) update of KOrganizer, it would send me loads of notifications from past events. It would only stop when I kill kalendarac's process.
Summary: After the 6.6.1 (25.12.1-1) update of KOrganizer, it would send me loads of n...
Status: RESOLVED INTENTIONAL
Alias: None
Product: Reminder Daemon
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.6.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-12 17:19 UTC by HeathenHacks
Modified: 2026-01-13 23:37 UTC (History)
2 users (show)

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 HeathenHacks 2026-01-12 17:19:26 UTC
SUMMARY

I started having this issue when KOrganizer was updated to 6.6.1 (25.12.1).

When I launch it, I would start getting bombarded by notifications from past events from last year, and would only stop once I kill kalendarac's process on btop.

STEPS TO REPRODUCE:
Not sure if reproducible.

OBSERVED RESULT:
Multiple notifications from last year's events.

EXPECTED RESULT:
Notifications of current day events.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.4-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 5070 Ti
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS MASTER
System Version: -CF

ADDITIONAL INFORMATION:
N/A
Comment 1 Albert Astals Cid 2026-01-12 17:26:35 UTC
Unfortunately there was a bug in which events that should have been reminded to you after rebooting the computer were not, because they were written to a place and read from another, we have fixed that now but it has the unfortunate effect that you are now receiving all this notifications.

I could not devise a plan that would fix both things reliably, maybe I should have thought more about it, apologies for that.

If you dismiss all the notifications, they should not show again after you reboot the computer.

If there are too many to handle manually, we can tell you the file that you manually have to edit to remove these old reminders.
Comment 2 Albert Astals Cid 2026-01-12 23:17:33 UTC
The file that you would have to play with is $(HOME)/.local/state/kalendaracstaterc 

You can remove everything from that file except the [Alarms] and [Suspend] groups (or you can remove that too, but then you will lose a bit of configuration)
Comment 3 HeathenHacks 2026-01-13 00:55:37 UTC
(In reply to Albert Astals Cid from comment #2)
> The file that you would have to play with is
> $(HOME)/.local/state/kalendaracstaterc 
> 
> You can remove everything from that file except the [Alarms] and [Suspend]
> groups (or you can remove that too, but then you will lose a bit of
> configuration)

That fixed it for me. 

Thank you!
Comment 4 HeathenHacks 2026-01-13 01:00:11 UTC
(In reply to Albert Astals Cid from comment #1)
> Unfortunately there was a bug in which events that should have been reminded
> to you after rebooting the computer were not, because they were written to a
> place and read from another, we have fixed that now but it has the
> unfortunate effect that you are now receiving all this notifications.
> 
> I could not devise a plan that would fix both things reliably, maybe I
> should have thought more about it, apologies for that.
> 
> If you dismiss all the notifications, they should not show again after you
> reboot the computer.
> 
> If there are too many to handle manually, we can tell you the file that you
> manually have to edit to remove these old reminders.

It's ok, it's working now. I have KOrganizer launch on startup anyway, so, I can see the events as well, even without the notifications.
Comment 5 Albert Astals Cid 2026-01-13 23:37:07 UTC
I am going to close the bug since at this point there's not much we can really do.