https://bugs.kde.org/show_bug.cgi?id=423043
--- Comment #1 from David Jarvie <djar...@kde.org> --- Perhaps step 42 will provide the answer after all (I hope) ;) What might fix this is to 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. With any luck, that will fix the problems you have seen. Yours is unfortunately one of too many bug reports which are due to Akonadi doing things wrong, in particular not saving calendar updates. For this reason, the next major release of KAlarm (version 3.0) will by default no longer use Akonadi (although Akonadi will remain as a build option), and the type of problem which you have seen should go away. KAlarm version 3.0 will be in the KDE 20.08 release in August. Since you use Gentoo, you could consider downloading the current git master branch for KAlarm, which contains the non-Akonadi build option. Of course, you would need to amend CMakeLists.txt to avoid the build pulling in newer versions of KDE Pim and Frameworks library dependencies. Whether you want to spend time doing that, or rather wait until August for the new release, is your choice. -- You are receiving this mail because: You are watching all bug changes.
