[Akonadi] [Bug 313670] New: DAV Akonadi resource falsely changes the mimetype of the todos to events

[Matija Šuklje]

https://bugs.kde.org/show_bug.cgi?id=313670

            Bug ID: 313670
           Summary: DAV Akonadi resource falsely changes the mimetype of
                    the todos to events
    Classification: Unclassified
           Product: Akonadi
           Version: 4.9
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: DAV Resource
          Assignee: kdepim-bugs at kde.org
          Reporter: matija at suklje.name

Akonadi’s DAV resource at some point in time — usually after a few days, but it
never fails me — changes the mimetypes of all items in the resource to
application/x-vnd.akonadi.calendar.event, regardless whether it’s raw output is
VTODO or VEVENT.

This happens regardless of whether a certain calendar in the resource includes
only VTODO, only VEVENT or both.

If I add new todo’s, until the next recurrence their mimetype stays as
application/x-vnd.akonadi.calendar.todo.

This is quite annoying for me because Zanshin only shows
application/x-vnd.akonadi.calendar.todo and not .event — meaning that I’m left
with empty todo lists. As KOrganizer and EventList do not do such filtering,
they show todos as well.

Reproducible: Always

Steps to Reproduce:
1. Create a calendar with that includes VTODO’s on a CalDAV resource;
2. Add the CalDAL resource to Akonadi;
3. Wait for a few days;
4. Check Zanshin and/or Akonadi Console.
Actual Results:  
- in Zanshin you see empty calendars;
- in Akonadi Console’s browser you can see that all the items were changed to
application/x-vnd.akonadi.calendar.event regardless whether their raw output
says it’s VTODO or VEVENT;
- in KOrganizer and EventList plasmoid you see VTODO’s as well.

Expected Results:  
- *keep* the mimetypes correctly — i.e. .event for VEVENT and .todo for VTODO

Workaround:
- in Akonadi Console remove DAV resource
- in Akonadi Console re-add the same DAV resource
(works also by simply cloning it)

Because a freshly (re)added resource fixes it, I’m suspecting it’s Akonadi that
messes things up.

Local iCal files and Kolab work just, fine, so I suspect it’s only the Akonadi
DAV resource. I heard that this used to happened also with the Google resource,
if it’s maybe related.

Versions:
KDE 4.9.3
Zanshin 0.2.1
Akonadi backend: MySQL
ownCloud: 4.5.5 (same issue with older versions), uses SabreDAV 1.6.4
Baïkal: 0.2.4, uses SabreDAV 1.8.0

-- 
You are receiving this mail because:
You are the assignee for the bug.