https://bugs.kde.org/show_bug.cgi?id=423406
--- Comment #3 from David Jarvie <djar...@kde.org> --- This doesn't happen on my system, so without more information on exactly where in akonadi_kalarm_resource CPU is being used, I can't investigate. This issue will go away in KAlarm version 3.0, which will no longer use Akonadi. It will be released as part of KDE release 20.08 in August. -- You are receiving this mail because: You are watching all bug changes.
