Version: 1.1 (using KDE 4.6.5) OS: Linux the summary view does not show upcoming events from additional calenders, such as e.g. akanodi-google. Setting the additional calendar as "standard" does not help either. Reproducible: Always Steps to Reproduce: open summary view Actual Results: no events from additional calendars are shown Expected Results: All upcoming events are shown OS: Linux (x86_64) release 2.6.37.6-0.5-default Compiler: gcc
please paste the kontact version (either in help/about Kontact or kontact --version)
Hi, my kontact version is 4.7 rc2 the summary version is 1.1
Same here, in the Summary, under the "Upcoming events" voice, the akonadi-google calendar isn't displayed, but a remote ics calendar is. Arch Linux x86_64 KDE 4.7.2
Same problem on Kubuntu 4.7.2
Hi, Same problem on opensuse 12 KDE 4.7.2 release 5 Kontact version 4.7.2 Summary version 1.1
same problem here, on lastest kubuntu (ppa) Plate-forme de développement de KDE : 4.8.00 (4.8.0 Kontact : 4.8.0 If it can help : it's the same for 'task' view in summary : only tasks from "invitations" calendar are shown.
by the way, it do work with kolab's calendar
Could it have something to do with the fact that the reminders don't work either in the akonadi-google calender plugin? (Reminders are simply missing when opening a google apointment in kontact).
Created attachment 70550 [details] kontact summary view Works fine here. See the attached screenshot. The events come from 3 different calendars, none of them is the default one. (two are remote ones, one comes from the akonadi-google resource)
Confirmed. Kontact 4.8.2, Kubuntu 12.04. I have only one calendar, akonadi_gcal_resource_0, and none of the events in that calendar show in the summary.
Confirmed (kde 4.12.2). I can see only events that recurs.. I created a patch to fix this issue. It fixes also another strange bug (that is difficult to explain, since my english is really poor): some event that recurs and that expires shortly after are reported as "next 00.00". This is because the next date is invalid, I added a simply check. I tested the patch with kde 4.12.2
Created attachment 85149 [details] patch
(In reply to comment #11) > Confirmed (kde 4.12.2). I can see only events that recurs.. > I created a patch to fix this issue. > It fixes also another strange bug (that is difficult to explain, since my > english is really poor): some event that recurs and that expires shortly > after are reported as "next 00.00". > This is because the next date is invalid, I added a simply check. > I tested the patch with kde 4.12.2 Confirmed for seeing only recurring events, and next 00.00. KDE Kontact 4.13.1 I'm a Linux noob on Kubuntu. How do I apply the patch?
Confirmed: seeing only recurring events, and next 00.00. Arch Linux, Kontact 4.13.2 Patch from Eugenio fixes this for me.
(In reply to Eugenio from comment #11) > Confirmed (kde 4.12.2). I can see only events that recurs.. > I created a patch to fix this issue. Sorry, but this does not seem to be related to the issue reported here at all. What you describe sounds like bug#327256. Btw, I created a patch myself yesterday to fix this (before I saw yours now) and have uploaded it to reviewboard, see the other bug report. > It fixes also another strange bug (that is difficult to explain, since my > english is really poor): some event that recurs and that expires shortly > after are reported as "next 00.00". > This is because the next date is invalid, I added a simply check. > I tested the patch with kde 4.12.2 Could you please open a new bug report for this? It's unrelated to both issues. Maybe you should upload the second part of your patch to reviewboard as well. It might get lost here.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.