@marki said in Event made private is not synchronized as private if before it was already synced while being public:
However I'd like to understand first how a client that would NOT actually retrieve the file knows that it has become private. Where is the protocol hint that the requested event has become private? (I found RFC 5545, Section 126.96.36.199 but which is not very explicit...)
I don't understand what you mean… as far as I have understood it by now:
When a user sets an event to private, the UA uploads the event with CLASS:PRIVATE to the server which causes the event to be changed (new ETag).
Users who still have access to the event (for instance, the owner) will from now on receive the updated event with CLASS:PRIVATE, so that the UA knows this event is private.
Users who don't have access to the event won't receive the event from now on (i.e. the server doesn't list it on PROPFIND or REPORT, and denies access on HEAD/GET). So, from their point of view, the event has gone and will be deleted with the next sync.
For CLASS:CONFIDENTIAL events, it's the same but the event is not gone for users who don't have access, but there are no event details (only a short event "user xx is busy" or something like that).
(I hope I didn't confuse PRIVATE with CONFIDENTIAL in this posting.)
Thanks for the URL. The problem are these lines:
ACKNOWLEDGED seems to be defined by this draft: https://tools.ietf.org/id/draft-daboo-valarm-extensions-04.html#rfc.section.8.1 and is understood and parsed by ical4j.
ACKNOWLEDGED is defined like this:
acknowledged = "ACKNOWLEDGED" acknowledgedparam ":" datetime CRLF
acknowledgedparam = *(
; the following is OPTIONAL,
; and MAY occur more than once
In your iCalendar resource, there are two colons (:), which is not parseable.
So, this is an invalid iCalendar file. Please fix the your iCalendar or report this problem (including this analysis) to someone who can fix it.
Output from sudo libinput list-devices | grep Device ...
libinput error: event17 - Network Tablet: libinput bug: missing tablet capabilities: resolution.Ignoring this device.
I tried starting the driver and device in a different order, in case resolution isn't set until the device first connects, but the error remains.
Is there any additional info I can provide to help debug this?