While these hundreds of pop-ups emerge, the system is irresponsive and afterwards, they have to be closed one-by-one to continue working normally. This is quite annoying as you can imagine (fortunately I don't have to manually start akonadi many times). I guess the issue depends on my own calendars and configuration, so not much people is affected (otherwise I assume it would have been already fixed). I'm willing to report more info and help testing if properly directed. In the meantime I'll try to silence these pop-up error messages.
Can you please provide a screenshot of the error message? I would be surprised if the dialog came from the actual resource, so I wonder if that's maybe KOrgac showing this. What's special about your configuration? Is that something I might be able to set up locally to try to reproduce the issue?
Created attachment 114601 [details] Error pop-up message
(In reply to Daniel Vrátil from comment #1) > Can you please provide a screenshot of the error message? I would be > surprised if the dialog came from the actual resource, so I wonder if that's > maybe KOrgac showing this. Sure, please see attached a screenshot. This time I got 28 error messages, which is not much, sometimes they are more than a hundred. Also, I sometimes get korganizer errors in addition to kontact, as indicated by the title of the pop-up error. This screenshot I took with my phone as my computer typically becomes irresponsive (kwin uses all CPU power) until I kill kontact (but then the errors disappear).
> What's special about your configuration? Is that something I might be able > to set up locally to try to reproduce the issue? I'm not sure there is anything special. I have the following calendars: - a local/personal calendar w/ change control - dates and birthdates calendar - invitations calendar - my google calendar - a third google calendar (configured as an ics)
I see that popup (in English) on occasion, but only one time, when I start up Plasma, at which point KOrganizer may or may not show any of my events (all should be from the Google Groupware calendar) see also bug 449024 for that problem, although I don't think they are related, as this happened even before it stopped retrieving the Google calendar data.