https://bugs.kde.org/show_bug.cgi?id=235690
--- Comment #13 from Martin Nebe <martin.n...@gmail.com> --- After another day of intense testing I have some more information about this bug: - Events that do not have a DTSTART entry, i.e. no starttime, will always cause Kontact to hang if the Plugin Name 'Calendar' has it's check box marked in the Summary Selection pane, no matter what choices one makes in the Upcoming Events Summary Setup pane. (I don't know how, but my friends Google calendar had three such entries, even though they did show start times in the Google web GUI. All of them were recurrent tasks.) - The Upcoming Special Dates will cause Kontact to hang for the same reason, but only if both 'Show birthdays' check boxes are marked in the Upcoming Special Dates Summary Setup pane. (There is one such check box under 'Show these Special Dates From Your Calendar', and another one under 'Show these Special Dates From Your Contact List'.) - My theory in Comment 10 was to simple, and therefore I have to rephrase it substantially to something like the following: Plugin summaries that query corrupted calenders can cause Kontact to hang when they e.g. encounter an event that do not have a start time or whose Remote Id is not unique in Akonadi. - The processor load gets close to 100% when this occurs so I guess the query gets stuck in a rather tight loop, sometimes causing my whole system to freeze! - So the most straight forward approach to palliate this problem is perhaps to add some code that replaces the hanging with an error message showing the 'Raw Payload' of the corrupted event in addition to the associated Id, Remote Id and the calendar name. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs