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-2022-4f28c7541d
Please login to add feedback.
0 | 6 | Test Case firefox addons |
0 | 11 | Test Case firefox browse |
-2 | 7 | Test Case firefox media |
0 | 3 | Test Case firefox screenshot |
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
LGTM. But automatic light/dark theme stopped working for me (X11). Current system theme is dark, but Firefox using light theme in Auto mode.
UPD: auto light/dark seems like upstream issue and Flathub build also have this issue.
Firefox 98 looks good.
There is a problem today with one of the webm test pages you use for the "media" tests. This isn't a Firefox problem. The video fails to play on Linux and Android, using Firefox, Chrome or Edge. https://webm.html5.org/ . It says "Trying to play video. Please wait" and doesn't play. (could be a temporary problem with the server they use)
You may want to switch that webm test to the detection page at https://www.webmproject.org/detect/
update: in the media tests, https://webm.html5.org/ requires that both audio and video autoplay is enabled or else it always says it is trying to play the video and you don't see the video control. I have audio autoplay turned off everywhere, that's why it always failed for me in different browsers on different devices. The web project seems a better test. It shows the video still and allows you to run it even if autoplay is blocked.
This update has been pushed to testing.
bump
Works.
Works. Thank you.
It seems VA-API acceleration is not working.
I forgot to mention if this might be due to the added support to ffmpeg 5.0 while Fedora 35 doesn't provide ffmpeg 5.0 in any capacity, so far.
Should it not submitted automatically to stable after all these positive karma?
It's probably due to the "2 of 57 required tests failed". The same thing happened with the F34 update.
No regressions detected (media.ffmpeg.vaapi.enabled set to default (false) so that was not tested).
LGTM.
"X" close icon is missing in one of the FF window.
This build of Firefox requires libwayland 1.20, downgrading libwayland to 1.19 crashes Firefox, the package dependencies would need to be updated to reflect that.
WFM
Works well
Given the security issues it fixes and all the positive karma, can this be pushed to stable please?
No regressions.
no regressions noted
The tests failed because of https://bugzilla.redhat.com/show_bug.cgi?id=2054953 (the tests expect to see that bookmark toolbar). That does seem like a real bug, but shouldn't hold up the update. I've adjusted the tests to soft-fail if the bookmark toolbar is missing and am re-running them now.
adamwill edited this update.
This update's test gating status has been changed to 'passed'.
This update can be pushed to stable now if the maintainer wishes
Looks like VA-API is broken on AMDGPU, it seems to actually be crashing the decoder process. See https://retrace.fedoraproject.org/faf/reports/370793/ and possibly https://bugzilla.mozilla.org/show_bug.cgi?id=1751363 (though in that case it seems to fall back to software decoding and not crash). This will likely cause some complaints for people where this was previously working.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
bump
This update has been submitted for stable by bodhi.
Works fine on Thinkpad P1 gen3 (Intel GPU).
@wayne6001 That was good feedback, thanks. I updated the test case. It's a wiki page, feel free to adjust it yourself next time, no worries :-)
This update has been pushed to stable.