https://bugzilla.redhat.com/show_bug.cgi?id=2177238
--- Comment #13 from Kamil Páral <kparal(a)redhat.com> ---
I found out more details:
* The event needs to be from Google calendar (or possibly other remote source),
it doesn't crash with a local calendar
* This is not about location, it also happens when I edit e.g. the event name
* To trigger this, I have to click on the event quite quickly after confirming
the change. It seems that if I click on the event before the change is
submitted to Google servers and then refreshed, it triggers this problem. If I
wait for a few seconds and then click on the event, it's fine.
* There are two options, either it crashes, or the window becomes unresponsive,
nothing can be clicked on, and it can't be closed either (gnome-shell doesn't
invoke the unresponsive window dialog, so the only option is to send sigterm to
the process, to close the window).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2177238