[Akonadi] [Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 Alexander Maret-Huskinson a...@maret.de changed: What|Removed |Added CC||a...@maret.de --- Comment #14 from Alexander Maret-Huskinson a...@maret.de --- (In reply to comment #11) 5. Change the value of collectionannotations (double-click) to /vendor/kolab/folder-type event.default /vendor/kolab/folder-type note.default /vendor/kolab/folder-type contact.default /vendor/kolab/folder-type task.default /vendor/kolab/folder-type journal.default depending on your need. Unfortunately this does not seem to work with 4.11.0. When changing the collectionannotations attribute I get the error message: Kolab: Parent collection can not contain sub-collections.. All my folders just get ignored and no contacts/events/notes/... are displayed in kontact. Any idea what's causing this? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 --- Comment #15 from Alexander Maret-Huskinson a...@maret.de --- Took me a while playing with the akonadiconsole but I figured it out: Kolab's Akonadi sub-collections can not be created because the parent collection which is created by the kolab proxy does not have the inode/directory content type set. You have to create it manually and then set the inode/directory content type. In case someone else runs into the same problem: Within akonadiconsole, you can use the debugger to see which commands are used to create the parent collection. Just paste them into the Raw Socket tab (starting from the 0 Login command), but do not paste the one that fails. You can now use the Browser and add the content type inode/directory to the newly created collection. From now on, Kolab will be able to create its collections whenever you add a collectionannotation to an IMAP folder. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 322404] New: DAV resource syncs calendar components even though they are not advertised by the server.
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
[Akonadi] [Bug 311240] CalDAV calendar resource shows duplicate calendar
https://bugs.kde.org/show_bug.cgi?id=311240 Alexander Maret-Huskinson a...@maret.de changed: What|Removed |Added CC||a...@maret.de --- Comment #4 from Alexander Maret-Huskinson a...@maret.de --- I got the same problem with Zarafa 7.1.x and KDE 4.10.0. There is only one Akonadi resource configured but KOrganizer displays two entries below the Zarafa tree item in the lower left section of the KOrganizer window where you can enable/disable each calendar. Clicking on one of the calendar entries will also enable/disable the other one. They seem to be linked together. -- 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
