Bug 352749 - Unable to sync calendar events from KOrganizer to the Kolab server
Summary: Unable to sync calendar events from KOrganizer to the Kolab server
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: GIT (master)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-15 14:53 UTC by Luca Beltrame
Modified: 2018-02-01 09:50 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 Luca Beltrame 2015-09-15 14:53:50 UTC
When creating events in KOrganizer using a Kolab resource, said events are not synced back to the Kolab server. Communication in the opposite way works well (events created e.g. in Roundcube will get synced back to KOrganizer).

Forcing a sync from KOrganizer doesn't help, either.

Reproducible: Always

Steps to Reproduce:
1. Create an event in KOrganizer and force a resource sync
2. Check the corresponding side on the server (e.g. in Roundcube) for the presence of the event


Actual Results:  
The event created in KOrganizer is not present on the server.

Expected Results:  
The event created in KOrganizer is present on the server.

Latest libkolab from the 1.0 branch, latest libkolabxml from master, git master of all frameworks and PIM.
Comment 1 Denis Kurz 2017-06-23 20:17:44 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:50:31 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.