| Summary: | KAlarm (Version 2.8.6-ak) will not save new alarm | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Maurice Batey <maurice> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | normal | CC: | maurice |
| Priority: | NOR | ||
| Version First Reported In: | KDE 4 | ||
| Target Milestone: | --- | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Maurice Batey
2013-03-19 18:36:51 UTC
Can you please check whether you have any enabled, writable active alarm calendar. Use the menu option View -> Show Calendars and with Active Alarms selected, check the status of the calendars displayed. The error you see will occur if there are none shown, or if none of them are ticked, or if when you hover the mouse over them they are shown as read-only. In that case, you need to either add a new calendar, enable a calendar by ticking it, or investigate why it is read-only (probably due to file permissions). The 'Active Alarms' entry was greyed out.
Fortunately a fellow Mageia user was able to point me at:
http://forum.kde.org/viewtopic.php?f=229&t=110230
and by using 'Add' for Active Alarms I was able to reconnect KAlarm with calendar.ics.
(How/why had it become disconnected?)
So I'm happy to report that new alarms *are* being stored, so the issue is RESOLVED.
Thank you for your prompt response - much appreciated!
In KDE 4.11, the user will be warned if KAlarm starts up without any enabled, writable calendars. This may help users to sort out the type of problem you describe. See bug 316338. Agreed! Apologies for leaving this open... |