| Summary | calendars are not published as read-only |
| Queue | Kronolith |
| Queue Version | 4.2.19 |
| Type | Bug |
| State | No Feedback |
| Priority | 2. Medium |
| Owners | |
| Requester | nobody (at) nothing (dot) com |
| Created | 03/21/2017 (3005 days ago) |
| Due | |
| Updated | 06/08/2017 (2926 days ago) |
| Assigned | 03/27/2017 (2999 days ago) |
| Resolved | 06/08/2017 (2926 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Feedback
synchronized, not the calendar itself.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ calendars are not published as read-only
Type ⇒ Bug
State ⇒ Unconfirmed
I can only assume that this is the issue:
when syncing Kronolith-calendars with Android using Davdroid, Davdroid
does not mark read only calendars as read only to the calendar app so
I can change entries in read-only calendars and get a crashing sync
when trying to sync back to the read-only calendar. Since the davdroid
guys say that davdroid can handle read-only calendars I assume
kronolith has a bug.
Here the report at the davdroid forum and probably some more follow-up:
https://forums.bitfire.at/topic/1372/read-only-calendars/3
regards