Comment # 10 on bug 954161 from Robin Roevens

(In reply to Dominique Leuenberger from comment #9)
> Feel free to work on it - then you can assign youself the priority you want.

Thanks for that gentle reminder. If I would have had the possibilities,
knowledge and capabilities I would have certainly done that, but that is
currently not the case. I already tried cooperating the best I can by analyzing
the problem and provide as much relevant information as possible for those with
the correct knowledge and/or capabilities (#c7). And I offer further
cooperation in finding the cause for this problem by testing and/or providing
any additional information if I know what to test or provide.. 

But absolutely no reaction came in over a month of time, hence I tried shaking
the tree a bit since this bug looks too serious and visible for an
"enterprise-grade stable" distro as Leap is supposed to be. And I didn't think
it would be too hard to fix as Tumbleweed does not have this problem. Only the
right person has had to give it a look..

> There is actually a good chance that libical 1.0 is at fault here too - we
> had seen identified other bugs caused by it.
> 
> please test to upgrade based on the repository:;
> http://download.opensuse.org/repositories/home:/fcrozat:/branches:/openSUSE:/
> Leap:/42.1:/Update/standard/
> 
> And report back

And it seems you where that right person since I upgraded the packages from
that repo per your suggestion and indeed this seems to fix the problem. 
I no longer see the recurring events from the past. Also browsing the calendar
in evolution now is again quite fluent without constantly crashing the calendar
back-ends.