Re: [Evolution] CalDAV is readonly


exactly, I'm on 3.34.3. I did indeed do several restarts (without

Thanks for your efforts though, I'll file a bug on github to keep track
of this and see if I am the only one who is affected by this.


On Thu, 2020-01-09 at 16:22 +0100, Milan Crha via evolution-list wrote:
On Thu, 2020-01-09 at 12:06 +0000, Krauß, Peter (SCC) via evolution-
list wrote:
However it is considered /readonly/ for some reason. How can I make
it writeable? I started the calendar factory in debug mode
(CALDAV_DEBUG=all and -w flag) to see what the server provides:

there used to be a problem that the read/write property changes were
not properly delivered to the client side, thus the client side
the calendar/book/... is read only, even though the backend side knew
it can also write to, not only read from.

It seems you use 3.34.3, probably both evolution-data-server and
evolution), which contains latest attempts to address this issue.

I do not think it always worked, but I think a restart of the
factory or the background processes sometimes helped. I suppose you
restarted the calendar factory process (when running it to get the
log), but it didn't help, right? I've no idea what to try next, the
snippets you showed looks fine.

evolution-list mailing list
evolution-list gnome org
To change your list options or unsubscribe, visit ...
Peter Krauß <peter krauss kit edu>

Karlsruher Institut für Technologie (KIT)
Steinbuch Centre for Computing (SCC)

Forschungsgruppe Cloud Computing
Hermann-von-Helmholtz-Platz 1
Gebäude 449/R105
76344 Eggenstein-Leopoldshafen

Telefon: +49(0)721/608-26578
E-Mail: peter krauss kit edu

KIT - Universität des Landes Baden-Württemberg und nationales
Forschungszentrum in der Helmholtz-Gemeinschaft

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]