This is for bug tracking purposes, for the details see https://gitlab.gnome.org/GNOME/gjs/-/issues/705 Reproducible: Always
Proposed as a Blocker for 43-final by Fedora user lruzicka using the blocker tracking app because: I believe that this behaviour violates the Default Application Functionality criterion, https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria#Default_application_functionality
+5 in https://pagure.io/fedora-qa/blocker-review/issue/1888 , marking accepted. I'm also gonna propose this as a Beta FE as the consequence of hitting it is pretty bad.
Discussed at the 2025-09-01 (blocker / freeze exception) review meeting: This is accepted as a Beta FE, as it's obviously a poor experience if turning on an accessibility feature causes recurring crashes, and we would like to avoid this in the Beta if possible, including on the live image and before the first update. https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-09-01/f43-blocker-review.2025-09-01-16.00.txt
Lukas, don't put commas in the whiteboard fields. Whiteboard is a free text string, not an array format, and we don't parse the commas, we rely on space separation. I don't totally remember how the queries in bz and blockerbugs work, but if one is looking for specifically "AcceptedBlocker" it might not match bugs which have "AcceptedBlocker,".
Lukas, I can no longer reproduce this with F43 Beta. Can you?
I can confirm that I cannot reproduce this issue on F43 Beta.
It was a problem in GNOME 49 Alpha, clearly it got resolved. Let's close it.