Bug 397408 - Deleting calendar event in DAV groupware resource fails
Summary: Deleting calendar event in DAV groupware resource fails
Status: RESOLVED DUPLICATE of bug 365080
Alias: None
Product: korganizer
Classification: Applications
Component: groupware (show other bugs)
Version: 5.8.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-13 00:11 UTC by Miroslav Vujicic
Modified: 2018-09-17 02:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miroslav Vujicic 2018-08-13 00:11:09 UTC
I can create and edit events in CalDav resources, but deleting fails.

If I try and delete an event I created, the event disappears from the local calendar view, but when I try to update the calendar folder I get "Before syncing <resource> it is necessary to have the resource online. Do you want to make it online?", and I click "Go Online". If I try to update the calendar again the same happens again - which means the upstream resource was not updated.

When I look in akonadiconsole, in Agents tab, next to the resource there is a Status Message:
"There was a problem with the request. The item has not been deleted from the server.
The file or folder <resource_XXXX> does not exist. (0)."

Once this happens, the only thing I can do (what I found so far) is delete the agent and re-create it.

I got the line from the calendar log:

Code: Select all
    2404:130:0:1000:4186:4465:8a69:1b4c - <user> [23/Apr/2018:06:27:11 +1200] "DELETE /caldav.php/<resource_path>/1518548964.R513.ics/ HTTP/1.1" 404 407 "-" "Mozilla/5.0 (X11; Linux x86_64) KHTML/5.38.0 (like Gecko) Konqueror/5 KIO/5.38"

I was told that trailing slash after 1518548964.R513.ics is probably the culprit.
Comment 1 Miroslav Vujicic 2018-09-17 02:51:49 UTC
*** Bug 365080 has been marked as a duplicate of this bug. ***
Comment 2 Miroslav Vujicic 2018-09-17 02:56:00 UTC

*** This bug has been marked as a duplicate of bug 365080 ***