| Summary: | KAlarm crash on adding existing KAlarm calendar to Kontact | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Fritigern <fritigerngothly> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version First Reported In: | 2.10.6-ak | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Fritigern
2013-10-21 18:09:06 UTC
The crash also occurs after a calendar is created in KAlarm which uses the same calendar file as another existing calendar. In this case, it crashes when the new calendar is enabled. Opening a KAlarm calendar in KOrganizer as an ICal calendar will lead to problems if KOrganizer updates the calendar. If it is configured as an ICal calendar, it should be set to read-only. A mechanism is required to prevent KAlarm calendars from being opened as read-write ICal calendars. This is not a straightforward problem. I can no longer reproduce this crash using the latest versions of KAlarm and KOrganizer, so marking as closed. |