https://bugs.kde.org/show_bug.cgi?id=470477
--- Comment #6 from David Jarvie <djar...@kde.org> ---
This problem is clearly due to Akonadi. It is because of its unreliability that
KAlarm (since version 3, released in 2020 in KDE Apps 20.08) no longer uses
Akonadi. Upgrading would be the most reliable way to fix the issue.
In the meantime, I suggest trying the following. In each case, quit KAlarm
first before running the fix. In a terminal window, run the commands
akonadictl vacuum
akonadictl fsck
If that doesn't fix things, run the commands
akonadictl stop
rm ~/.config/akonadi_*kalarm*rc
rm ~/.config/akonadi/*_kalarm*
If that still doesn't fix things, all I can think of is to completely wipe
Akonadi's configuration. WARNING: this should only be done if you don't use any
other KDE PIM applications which use Akonadi, such as KMail, KOrganizer, KNotes
(and possibly others), since those applications could lose data. It would be
wise to back up all files and directories before deleting them, so that you can
reinstate them afterwards if things go wrong. To wipe the Akonadi
configuration,
akonadictl stop
rm -rf ~/.config/akonadi*
rm -rf ~/.local/share/akonadi*
--
You are receiving this mail because:
You are watching all bug changes.
