FinalBlocker +1

I want us to apply the application basic functionality criterion less often and less strictly, so we block releases on it less often. But it's always going to be subjective and I'd say this crosses the line. Too embarrassing.

FinalBlocker +1

I wrote my experience here:
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1087#note_1837091

I didn't try to reopen Calendar quickly, I just leisurely closed it, open it again, and I saw that issue. After opening it a few times, it became unusable because it was so slow. I agree that this really prevents basic functionality.

FinalBlocker +1

FinalBlocker +1
AGREED AcceptedFinalBlocker

The following votes have been closed:

• Accepted FinalBlocker (+4, 0, -0)
  • +1 by catanzaro, lruzicka, kparal, adamwill

For what it's worth, I'm not convinced that this issue should be a blocker. The duplicate events aren't written anywhere and, at least in my testing, aren't immediately apparent - you have to do some scrolling to come across them.

I initially wanted to vote -1. It was the performance impact that changed my mind. I literally couldn't use Calendar after a while, because it took half a minute for my events to show up after opening the Calendar, and I couldn't scroll at all, it just froze for tens of seconds with each scroll attempt.

Release F39 is no longer tracked by BlockerBugs, closing this ticket.