https://bugs.kde.org/show_bug.cgi?id=455377
David Jarvie <djar...@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REPORTED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- >From version 3.0 (KDE Apps 20.08), KAlarm no longer uses Akonadi, which fixes this issue. The decision to stop using Akonadi was due to the number of problems which kept arising with Akonadi - your issue is just one example of this, unfortunately. I'm not aware of any way of upgrading KAlarm by itself, so in order to KAlarm version 3 or later, you would probably have to upgrade KDE as a whole, which is likely to require a distro upgrade. You may be able to partially fix your problem with your current version as follows: 1) In the KAlarm main window, display the Calendars panel (using View -> Show Calendars) and select the calendar type of Archived Alarms. Hover over the listed resource (which will probably be called "Archived Alarms" to find out its file location, and note the location for later. 2) Ensure that no KAlarm alarm messages are currently displayed, and stop KAlarm by File -> Quit. (Or kill kalarm from the command line.) 3) Run akonadiconsole. In the Agents tab, select KAlarm's Archived Alarms, and remove it. 4) Run KAlarm again. It should recreate the archived alarms resource - check that it has done so by again looking at the archived alarms in the Calendars panel. A single calendar "Archived Alarms" should be listed (as before). If not, click Add and enter the noted file location, select alarm type Archived Alarms, and give it the display name "Archived Alarms". 5) Check whether this has improved the CPU consumption for the akaondi_kalarm_resource_* processes. I'm not sure whether creating a new KAlarm Directory resource works, so if you try to do the same for the Active Alarms calendar, you might possibly be unable to access your active alarms afterwards. You may just have to live with the problem until you are able to update to KAlarm version 3. -- You are receiving this mail because: You are watching all bug changes.