Bug 332889 - Setting active alarm calendar to read-only in Akonadi makes calendar unusable
Summary: Setting active alarm calendar to read-only in Akonadi makes calendar unusable
Status: CLOSED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: Akonadi (show other bugs)
Version: 2.10.6-ak
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-31 23:10 UTC by David Jarvie
Modified: 2020-08-17 23:37 UTC (History)
0 users

See Also:
Latest Commit: 69dbf8e16dbab06bbc9e65017c2a2d586757a5a1
Version Fixed In: 4.12.5

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David Jarvie 2014-03-31 23:10:31 UTC 
Use Akonadiconsole to configure the active alarms resource natively, and select read-only. This deletes the existing collection and creates a new one which has no KAlarmCollection or KAlarmCompatibility attributes. This makes it impossible to make the calendar usable again unless Akonadiconsole is used to delete the resource, before recreating the resource.

Reproducible: Always
Comment 1 David Jarvie 2014-04-01 22:17:49 UTC 
Ensure that a KAlarmCompatibility attribute is added to every new collection, so that if it is a compatible format, it can be recognised as a potentially writable calendar. Git commit 69dbf8e16dbab06bbc9e65017c2a2d586757a5a1 (KDE 4.12 branch).
Comment 2 David Jarvie 2014-08-24 23:30:13 UTC 
Fixed in KDE 4.12.5 and 4.13.0.