Bug 342569 - caldav calendar not shown / not synchronized any more
Summary: caldav calendar not shown / not synchronized any more
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (show other bugs)
Version: 4.13.2
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-06 22:05 UTC by Helmut Fedder
Modified: 2018-02-01 09:52 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 Helmut Fedder 2015-01-06 22:05:08 UTC
I had a working caldav resource.

Since today the calendar entries are not shown any more.

The calendar ispresent in the calendar list and I can check the "sub-calendars", however, no entries are shown.

Thank you for your help!

HF

Reproducible: Always

Steps to Reproduce:
1. open kontact
2. select kalendar component
3.

Actual Results:  
Calendar entries from a caldav resource are not shown

Expected Results:  
see the calendar entries
Comment 1 Benedikt Bauer 2015-01-07 12:59:49 UTC
I can confirm that on 4.14.2 on Kubuntu 12.04, however, only for one of the calendars of my ownCloud ressource – the other calendars on that server are displayed correctly. If I open the corresponding calendar in the aconadiconsole, all entries are there, they are just not displayed in the kalendar view of Kontact.
Comment 2 Helmut Fedder 2015-03-01 12:48:31 UTC
I am still having this issue. Currently I have to use my mobile phone for all work planning. This is quite annoying. I would be very happy if somebody could help me debugging.
Comment 3 Helmut Fedder 2015-04-15 07:24:42 UTC
Anyone who could help?
Comment 4 Denis Kurz 2017-06-23 19:37:03 UTC
This bug has never been confirmed for a Kontact 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 5 Denis Kurz 2018-02-01 09:52:04 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.