https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #2 from David Jarvie <djar...@kde.org> --- Thank you for the good quality bug report. Even with the information you provided, it isn't clear what went wrong. It's possible (but not certain) that if any events have UIDs which are duplicated between different active alarm calendar files, this may be able to trigger the crash. To help narrow down the cause, could you please check for duplicated event UIDs as follows: Check all the *active* alarm calendar files which were enabled in the left pane of the KAlarm main window, and also the calendar which you were activating when the crash occurred. To do this, execute the command grep ^UID: file1 file2 ... | sort | uniq -c | grep -v ^1 (substituting the actual file names, of course) This should output all event UIDs which are duplicated. If there are any duplicated UIDs, please check whether any or all of them occur in the calendar which caused the crash, by grepping within that file for the duplicated UIDs. -- You are receiving this mail because: You are watching all bug changes.
