@treba, thanks for the explanation. would be nice in the future (especially for things as critical as Fx and for such a noticeable defect) there would be a warning or notification posted on the change so when people are testing they would be aware. I understand that everyone can't be warned of everything, but if we're aware, it would be nice to make an attempt so people don't spin their wheels for nothing.
There is an unbelievable atrocious slowness when trying to use Fx Wayland on KDE - which is additionally very concerning since F34 is slated to have Plasma Wayland as the default. Previous version worked fine. Workaround is to use X11 version, which appears to run fine. I see from the comments in the spec file that the wayland backend was disabled... which would imply to me that folks that are on kde wayland that were using fx-wayland wouldn't be affected... that whatever would be done in the background - but that doesn't appear to be the case.
Thanks for your work on getting this applied so quickly. Much appreciated! Circumvents the current issue, but concerned it does not appear to be a long term solution. I updated BZ#1912046. When this issue surfaces, it is extremely disruptive.
Guys, this update needs to be pulled immediately - it simply isn't acceptable to delay and have a discussion about it. It's wreaking havoc. It is completely unacceptable to have something causing such disruption still in updates-testing going on 48 hours now.