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-2026-1d2f0d6cd6Please log in to add feedback.
| 0 | 1 | Test Case firefox addons |
| 0 | 2 | 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 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Thanks!
WFM.
This update has been submitted for stable by bodhi.
152.0.5 is out: https://www.firefox.com/en-US/firefox/152.0.5/releasenotes/
Only one fix mentioned.
We will never win this race. We are like a squirrel in a wheel, but in our case the wheel has brakes of Fedora delays. Interesting how important all those patches in the https://src.fedoraproject.org/rpms/firefox/tree/f44 are?
This update has been pushed to stable.
We're mostly fine now. Do we want to kick off the new build @stransky?
Could we maybe switch to a bundled version of libvpx until the update for the system package is available? Or is there a chance that it'll be addressed soon? @stransky Sorry for mentioning this here, but it seems that the issue has been present for a while now: https://bugzilla.redhat.com/show_bug.cgi?id=2440345
AFAIK pure libvpx is used for media encoding for WebRTC calls only - video decoding is done by ffmpeg/ffvpx.
@stransky I wasn't aware of this - but doesn't ffmpeg use libvpx?
As far as I can see, it has the flag
--enable-libvpxand according toldd, it loads libvpx. I think that to force the use of ffvpx, ffmpeg would need to be compiled with the flag--disable-libvpx. Maybe I'm missing something. It's possible that firefox specifically requests ffvpx, for example.AFAIK ffmpeg doesn't use libvpx (at least for regular video decoding). It has it's own decoding implementation.
ffvpx is Firefox ffmpeg bundle without patented codecs - it's not libvpx. It's possible that Firefox also has bundled libvpx library but that's used for WebRTC only afaik (also WebRTC is partially directed to use media decode/encode path which is ffmpeg/ffvpx).
AFAIK libxpv on Firefox side is used only to encode outgoing WebRTC video streams.
I've just found a useful official site of the Mozilla project with schedules and planned dates of all future major and patch level releases of Firefox: https://whattrainisitnow.com/ For instance according to https://whattrainisitnow.com/release/?version=release the next 152.0.x patch level release is currently planned for July 14 and according to https://whattrainisitnow.com/release/?version=beta the next 153.0 major release is planned for July 21. @stransky maybe it's worth to make a simple script that will check that site periodically once a day and inform you and other Fedora maintainers (related to the Firefox packages of Fedora) about any change or update in those two schedules? Or maybe something like that already exists and I just don't know?
I'm getting mail notifications about new releases but I was on PTO last two weeks. AFAIK the dot releases usually do not contain critical updates so I ship them when I have time in my regular workflow.