https://bugs.kde.org/show_bug.cgi?id=322404
Bug ID: 322404 Summary: DAV resource syncs calendar components even though they are not advertised by the server. Classification: Unclassified Product: Akonadi Version: 4.10 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: a...@maret.de Since KDE 4.10.5 I'm no longer able to sync my Zarafa caldav calendar because Akonadi tries to sync calendar components even though they are not advertised by the CALDAV:supported-calendar-component-set property. This becomes a problem because Akonadi seems to abort the whole sync process if an error occurs while trying to sync any of the calendar components. Therefore the VEVENT calendar will not be synced even though the error occurs when trying to sync the unsupported VJOURNAL component. The problem only occurs because Zarafa also has a bug which triggers an internal server error when trying to sync the unsupported calendar component VJOURNAL. The server however correctly advertises only the VEVENT and VTODO components, so KDE should either not try to sync the VJOURNAL component at all or ignore any errors which are triggered when trying to query components which were not advertised by the server. Reproducible: Always Steps to Reproduce: 1. Add a Zarafa 7.1.2-39121 caldav resource. 2. Sync the calendar. Actual Results: The calendar sync is aborted. Expected Results: The calendar should be synced successfully. Tested with: - OpenSuse 12.3 + KDE 4.10.5 - Kubuntu 12.04 + KDE 4.10.5 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs