kontact is set to display events of the next 7 days randomly but 99 % of the time nothing is displayed in the summary . i have this phenomenon with akonadi kde calendar or akonadi google calendar . procedure to experiment this pb : open a kde session kontact is launched (the last one) summary is displayed nothing in the event list if i relaunch kontact during kde session then same pb same pb for mail list i assume : - a bad synchro between the time when kontact summary gets data and akonadi is ready to serve data during kde session opening - kontact does not renew its summary during kde session Reproducible: Always
Created attachment 84848 [details] 0 event in the event list of the summary in the delay of 7 days
Created attachment 84849 [details] 2 events in the delay of 7 days
Same problem here. Chakra-Linux system. Latest kde upgrades 4.12.2-1
I came here to report this same bug, (still) present in 4.12.2
May be related with https://bugs.kde.org/show_bug.cgi?id=327256
Hi all! I have the same problem. KDE 4.12.3. This problem occur a very long time. :-( Best Regards, Simon
more info : precisely if the delay for an event is exactly 7 days from the current day then it is displayed but if the delay < 7 days it is not displayed
if the delay is 0 then the event is displayed to sum up : if 0 < delay < 7 then the event is not displayed
on opensuse 13.1 with kde 4.13.1 I think I have the same problem. In summary view only those events are shown that are today or on that day that is after the number of days set in the configuration minus 1. Example: if I set a period of 14 days to show the upcoming events, the events of today and day 13 are shown. Bug 278956 has a patch (in comment #12) which solves this bug for me. (My calendar is in owncloud).
Gentoo kontact 4.12.5 exact the same problem.
(In reply to Brallan Aguilar from comment #5) > May be related with https://bugs.kde.org/show_bug.cgi?id=327256 I agree, IMHO this does indeed sound like the same problem. I'm marking this report as duplicate, as the other one is older. Please feel free to reopen if you disagree. *** This bug has been marked as a duplicate of bug 327256 ***