https://bugs.kde.org/show_bug.cgi?id=470477
--- Comment #5 from van.sny...@sbcglobal.net <van.sny...@sbcglobal.net> --- On Thu, 2023-06-01 at 20:34 +0000, David Jarvie wrote: > https://bugs.kde.org/show_bug.cgi?id=470477 > > --- Comment #3 from David Jarvie <djar...@kde.org> ---A possible fix > is to right click on the alarm calendar in the calendar viewpanel, > and ensure that "Use as default for active alarms" is selected. > However, if the calendar is already selected as default, or if it > still doesn'twork after doing that, I suggest deleting and re-adding > the alarm calendar asfollows: > 1) Select the active alarm calendar in the calendar view panel, and > click ShowDetails. Note the File location.2) Remove it from KAlarm's > database by clicking Remove. (Note that this doesn'tdelete your > actual alarm calendar file.)3) Add the calendar again by clicking > Add. In the dialog, enter the filelocation noted in step 1, select > Active Alarms, enter "Active Alarms" as thename, and do not select > read only. After doing both sets of steps, it still refuses to create alarms. The "Active Alarms" calendar is not read only. It is enabled, and is the default calendar. Are there any secret incantations that can be invoked when launching kalarm so that it produces messages about why things went wrong? -- You are receiving this mail because: You are watching all bug changes.
