GNOME Bugzilla – Bug 789686
Caldav issues
Last modified: 2021-05-19 12:27:04 UTC
Created attachment 362601 [details] Test case: Calendar appointment from Deutsche Bahn AG I noticed a series of issues with caldav when switching to Ubuntu 17.10. Everything worked fine with Ubuntu GNOME 17.04. Error message during ics import: "Cannot receive calendar objects: Failed to put data: HTTP error code 201 (Created): The server responded with an HTML page, which can mean there’s an error on the server or with the client request." The import successfully finished regardless. It's still a nuisance. Creating new tasks: Same error message as for ics import. Tasks are only stored when date *and* time are specified. Error message needs to be ignored and window to be close with 'discard changes'. Update of calender appointments (external): just does not work Could not test handling of confirmations of meeting invites, yet. Calendar is hosted on a Synology DS214 NAS. I had to add a slash "/" at the end of the URL to have access after upgrade from version 3.24. Switch back to Thunderbird and Lightning as a workaround. Test case for import attached. Warm regards, Jürgen
Please file one task per problem as this task cannot be handled if it contains multiple unrelated issues. See and follow https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/Guidelines - Thanks! Also see https://wiki.gnome.org/Apps/Evolution/Debugging#CalDAV how to provide debug output which would be needed here. I imported your attached file into Evolution 3.26.1 and it is displayed correctly on my local calendar. Don't have a CalDAV instance here.
I apologize. I am an average and not a programmer. I do not know how to set environment variables for debugging and the instructions and not sufficient for my level of expertise. I had the impression that all errors have the same root cause that might be related to some unexpected code send back form the calendar server (or code that is handled differently, now). Please feel free to inactivate the report. I won't use evolution in the future and turn back to Thunderbird. Somewhat a bit given that evolution worked well in version 3.24. Best regards, Jürgen
Will not use evolution, anymore
If anything is unclear on https://wiki.gnome.org/Apps/Evolution/Debugging#CalDAV feel free to ask specific questions - happy to help debugging, but we cannot do the "reproducing" part for you. :)
Did some further testing (Fedora 27 with evolution: same issue; alternative caldav server: Radical as local server worked fine). Got the impression that version 3.26 does is not downward compatible with 'older' caldav server versions. Interestingly, debugging did not generate any messages (setting: CALDAV_DEBUG=message:header,items,attachments /usr/lib/evolution/evolution-calendar-factory >& logfile). Fortunately, an alternative caldav server (through Calendar app) became available by Synology. Gnome 3.26 works fine with that server. Required migration of calendar and task list, though. Used Thunderbird to export calendar to an ics file that I was able to import with evolution. Problem solved for me.
Comments regarding https://wiki.gnome.org/Apps/Evolution/Debugging#CalDAV - Would be to mention that you have to run these as commands from a terminal and evolution had to be started as a separate process. I was wondering as to how to set environment variables - There is no hint as to how to stop the process. I killed it by simply closing the terminal - I had to figure out that I had to entire paths to evolution-calendar-factory, i.e., the command did not work 'out of the box - Some examples may be helpful to unexperienced users
Created attachment 374227 [details] Log of successful event creation reported as failed with error 201 (Created) So I'm still encountering this issue two years later, with WebDAV running on a fully-updated Synology NAS, and it was all working fine until I upgraded from Debian stretch (evolution 3.22.6-1+deb9u2) to buster (evolution 3.30.5-1.1). It seems to me that evolution's reporting 201 (Created) as an error in response to an attempt to create an event (which *is* successfully created: it's turning up on other clients of the same calendar) can't be right. The error message in the GUI is as follows: Failed to create an event in the calendar “CalDAV : My Calendar” Cannot create calendar object: Failed to put data: HTTP error code 201 (Created): The server responded with an HTML page, which can mean there’s an error on the server or with the client request. The used URI was: https://my.host:999/webdav/calendars/my_calendar/1e86ff2bb119228877ffbf6871896a64c74a0e4d.ics Indeed, the HTML page returned by the server is just a "successful creation" message. It's a long time since I worked on WebDAV, but I seem to remember that unexpected content in a response body was to be ignored in favour of just using the numeric response code; maybe things have changed since then? Log file attached (host name, calendar name, port number, username all altered!).
(.. and while the misinterpretation of 201 is just inconvenient for create, it disrupts more complex actions, such as moving an item to another calendar - which fails after the item has been copied, but before the original has been removed.)
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.