And here we yet don’t have Firefox 150 on fedora 43…
Even fedora 42 users got it already!
What’s the blocker?
sudo dnf update --refresh --enablerepo=updates-testing firefox nss
and you are done.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c0a4f03150
Hi @fkrenzel, could you clarify why this update was pushed to F42 and F44, but not to F43? thanks!
For what it’s worth, Mozilla now publishes an RPM repo with up-to-date versions of Firefox, that’s usable in Fedora: Install Firefox on Linux | Firefox Help
At least on my device, instead of just installing or upgrading, I needed to specify the new version of Firefox, and I needed to allow erasing packages to remove the language packs that are packaged for the Fedora version: sudo dnf install firefox-150.0.1-1 --allowerasing
Exactly! I think the maintainer is (temporarily) unavailable?!
In that case, someone else should push the update to f43 as well if there’s no issues…
I wish Fedora Project had more people who give acare about things 
Based on the level of thought and work that seems to go into the project overall, I would assume things like this are caused by process issues. Perhaps there’s a gap in how single upstream releases are coordinated across separate maintainers, some of whom may not be primary for a package, across different Fedora releases. If not that, I would assume simple time/capacity issues for maintainers, as this is volunteer work for many.
Just speaking from my own experience in paid working environments, stating that process misses are because existing folks don’t care seems more likely to demotivate further work than rally folks to help.
One may argue that caring about process improvement is a prerequisite to improving process.
@stransky is also a Firefox maintainer.
I’ve pushed this one stable now.
Frankly, the worst part about this is the lack of communication.
Going by his “last bodhi-related activity”, he remains active over there.
While helping others for free is something worthy of respect, FOSS people often conveniently forget that volunteers do have responsibilities. If one intends to maintain an important piece of software, yet cannot (or doesn’t want to) update it in a timely manner, they should not apply – simple as that.
I don’t think it is a lack of care at all.
Generally speaking the firefox updates normally have set “autopush by karma” turned on which for those unaware means the update will get pushed to stable automatically when it hits +3 karma (I think this number is configurable but not 100% certain).
However, this was turned off for this update (including F42 & FF44) and I would prefer to believe that the updater/maintainer just wasn’t used to having to manually push to stable when in the past it was done automatically after our gracious QA team & volunteer testers gave the thumbs up.
Meanwhile, Firefox 150.0.1 has been released with even more security fixes… around a week ago.
@adamwill If you could prod the relevant people, it would be much appreciated.
If my memory serves me right, Firefox in Fedora 43 for quite some time, right after release, had been version behind F42 as well.
Incidentally, does anyone have any experience with Firefox from Mozilla’s official RPM repo?
I request the fedora management to look at this “firefox” situation. firefox must, as far as my knowledge goes, should be considered as a “critical” package, as it ships by default and is the only available web browser by default.
Continuous delay of updates is bad, very bad.
“Use the Mozilla RPM package” is a workaround, not a solution.
I concur.
@jspaleta Apologies for the ping, but could we escalate this somehow?
For whatever one opinion is worth - the commits to the Fedora Firefox package look to be majority one person, especially for upstream releases. Others are hopping in for fixes, but are there folks volunteering to build up the personal knowledge base needed to share the ongoing, version-after-version packaging load?
As far as I know, it’s not a situation like in a corporation where there is a “management” group that has folks at their disposal who are waiting for directions, and who are beholden to work on whatever is directed.
Correct me if I’m wrong, but as far as I can tell, M. Stransky is not a random volunteer – he works for Red Hat, and maintains Mozilla packages for both RHEL and Fedora; he’s also a major upstream contributor.