Bug 344077 - Calendar of Events ownCloud instance are not included in kontact Calendar
Summary: Calendar of Events ownCloud instance are not included in kontact Calendar
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: kdepim bugs
Depends on:
Reported: 2015-02-12 12:09 UTC by bluelupo
Modified: 2018-02-01 09:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description bluelupo 2015-02-12 12:09:58 UTC
A newly created Akonadi resource for a ownCloud instance (version 7.0.3) on a server of my provider may not be covered by the present konact calendar dates. A comparison of the data takes place every five minutes. Errors. A newly created date in the calendar kontact other hand, is transmitted to the ownCloud instance (visible in the web frontend).

A manual synchronic kidney of the calendar is not successful. What you can do is to look at the existing appointments in the calendar kontact.

Reproducible: Always

Actual Results:  
No Matches ownCloud instance in kontact calendar available.

versions from system:

kdepim-kresources 4:4.14.2-2
kdepim-runtime 4:4.14.2-3
kmail 4:4.14.2-2
kontact 4:4.14.2-2
akonadi-backend-sqlite 1.13.0-2
akonadi-server 1.13.0-2
akonadiconsole 4:4.14.2-2 

system: siduction 14.1.0 Indian Summer - kde (based on Debian Unstable)
kernel version: 3.19-0.towo-siduction-amd64

Do you need some additional information from my system?

Comment 1 Denis Kurz 2017-06-23 20:02:47 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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:46:25 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.