https://bugs.kde.org/show_bug.cgi?id=405313
--- Comment #22 from David Jarvie <djar...@kde.org> --- If you kill kalarm first, does it freeze again after restarting it and trying to do step 1? One thing which might possibly help to stop KAlarm freezing would be to delete its Akonadi data (which is separate from the alarm calendar data, so you won't lose any KAlarm data). The easy way to do this is to delete ALL Akonadi data - but beware that this will also delete some KMail, KOrganizer and possibly other KDE PIM applications' data, so it is not a good idea if you use any of them as well. If you really want to delete all Akonadi data, use the command 'rm -rf ~/.local/share/akonadi' If you don't want to delete all Akonadi data, proceed as follows: 1. Run "akonadiconsole" and look in the displayed list for all resources identified by the KAlarm icon. 2. For each KAlarm resource, double click on it to display its configuration, and note the File name, Display name and Alarm types shown for it. Close the configuration dialog, and then use the Remove button to remove the resource. Note that this does not delete the calendar file containing your alarms - it just removes KAlarm's reference to it. 3. Once you have removed all KAlarm resources, reinstate them. For each resource you have removed, click the Add button, select "KAlarm Calendar File" in the list of resource types, and in the configuration dialog enter the configuration details which you noted down for that resource in step 2. 4. You can now close akonadiconsole. 5. Test to see if KAlarm will now run without freezing. -- You are receiving this mail because: You are watching all bug changes.
