Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-e440aa9307Please log in to add feedback.
| 0 | 0 | Test Case firefox addons |
| 0 | 4 | Test Case firefox browse |
| 0 | 2 | Test Case firefox media |
| 0 | 2 | Test Case firefox screenshot |
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
Please install with FEDORA-2021-2c3da66ad5
This update's test gating status has been changed to 'ignored'.
Works well here. Only regression I see is that older devices (without GLES 3 support) loose WebGL because a fix-backport didn't make it to release, see https://bugzilla.mozilla.org/show_bug.cgi?id=1689207#c23
So in case there's another build it could make sense to include that one.
This update has been submitted for stable by bodhi.
Unable to install all-addons: Package mozilla-filesystem-1.9-23.fc33.x86_64 is already installed. Package mozilla-openh264-2.1.1-1.fc33.x86_64 is already installed. Error: Problem 1: conflicting requests - nothing provides npm(bindings) needed by mozilla-iot-gateway-0.9.2-4.fc33.noarch - nothing provides npm(nan) needed by mozilla-iot-gateway-0.9.2-4.fc33.noarch - nothing provides npm(sqlite3) needed by mozilla-iot-gateway-0.9.2-4.fc33.noarch Problem 2: conflicting requests - nothing provides npm(sqlite3) needed by mozilla-iot-gateway-addon-node-0.9.0-3.fc33.noarch (try to add '--skip-broken' to skip uninstallable packages)
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.
gbcox: this is due to a bug in Kwin that got fixed in plasma 5.21 so it will work in F34 (but unfortunately didn't get backported to 5.20). On F33 the Wayland backend is not enabled by default, so no reason to block the update for F33. A workaround it so set
widget.wayland_vsync.enabledtofalse.This update has been pushed to stable.
@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.
WFM on Gnome (Xorg).