https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #4 from David Jarvie <djar...@kde.org> --- The valgrind crash is in fact different from the original crash. The valgrind crash shows that multiple calendar status changes are being received in AlarmCalendar, before the processing of the previous one has completed. The fix for this will be to ensure that these status indications are queued so that they are never processed in parallel. The original crash only shows one calendar status change, so my previous Comment #2 and Comment #3 are still valid. -- You are receiving this mail because: You are watching all bug changes.
