Why do I have 33 akonadi_kalarm_resource processes running on my system?

Code: Select all

/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_10
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_11
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_12
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_13
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_14
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_15
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_16
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_17
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_18
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_19
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_20
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_21
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_22
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_23
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_24
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_25
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_26
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_27
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_28
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_29
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_30
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_31
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_32
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_33
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_34
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_35
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_36
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_37
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_5
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_6
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_7
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_8
/usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_9


This is one of many issues which KAlarm has had with Akonadi, and for this reason, recent versions of KAlarm (since version 3.0, which appeared in KDE apps 20.08) no longer use Akonadi to access calendars. Using KAlarm 3.0 or later will therefore fix the problem you have seen.

In the meantime, to fix the issue with your current version, you should delete all KAlarm's Akonadi active alarm resources, and then recreate them. To do this, first quit kalarm. Then run akonadiconsole (which you might have to install), and in its Agents tab, select each of the active alarm resources in turn and delete them. This won't affect the calendar files which they use.

Now start KAlarm again. It should recreate the Akonadi resource for ~/.local/share/kalarm/calendar.ics, or if not, use the Add button in the Calendars panel (accessed by View Calendars) to recreate it. If there are any other calendars which you want to use, add them here as well.

This issue was addressed in https://bugs.kde.org/show_bug.cgi?id=423043.

Thank you for your detailed and informative reply. I've done as you suggested and, unsurprisingly, those processes have disappeared.