I have read-only access to a calendar (ical calendar file) on goole, something like this: https://www.google.com/calendar/ical/XXXXXX@gmail.com/private-XXXXXXX/basic.ics (sensitive stuff XX'd out) When that calendar has two whole-day events on the same day, those get redrawn every second or two, in random order. That makes the display flicker in a most irritating way. This only happens with this one calendar. When running korganizer from the command like, the console fills up with messages like this: korganizer(32698) EventViews::AgendaView::Private::calendarIncidenceChanged: AgendaView::calendarIncidenceChanged() Invalid agendaItem for incidence "tp6vcg8ie0nag82qh7a6rgmaug@google.com" Each message seems to be repeated twice, and then a new one is displayed, with a different incidence number. I have verified that this happens on a freshly created account. Korganizer seems to eat about 50% of CPU when flickering like this, plasma-desktop another 50%, and mysql and akonadi servers seem to be active too... This seems not to happen with other remote ical files (fish: to my own server). I could not test on other google ical files, as I don't use google very much. I suspect that google's ical format is not quite what KOrganizer expects, but what do I know... All this on a freshly installed Debian/Jessie, Korganizer version 4.14 (not (yet?) in the bug report version list). Reproducible: Always
I see this too (also with packages in Jessie). This is also with google ical resources but not only for full day events and not only for clashing events. akonadiconsole shows that the resource is "Running" and "Downloading remote file" every 2 seconds. The only way to calm the CPU usage of akonadiserver (40% CPU), mysqld (40% CPU) and the akonadi_agent (20% CPU) is to put the resource offline, which isn't really desirable. In contrast the "Google Calenders and Tasks" resource works really well (providing you have authenticated access to the ical resource you want to look at)
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.
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.