When I said fairly easy - it is about the package itself.
What happens with the profile and the data stored there - that is entirely another story - which no amount of packaging can change.
Do you know, how i should delete firefox-137.0-1-x86_64.pkg.tar.zst that it wont get any longer detected by firefox?
Is there a pamac command?
You can add firefox to the list of ignored packages
Perhaps you should put in the firefox-ia8n-<something> as well
Or bite the apple and be done with it…
Nah i want to delete it, that the detection from firefox no longer shows me that im using a older version.
firefox-137.0-1-x86_64.pkg.tar.zst needs to be removed… if pamac showing me a newer version thats okay.
I think we have a misunderstanding:
This update checks are a Windows Firefox feature…
We are updating under Linux with a Package Manager anyways.
The problem that i have with this pop up, is not happening because there is a newer version available on the internet… it is popping up because of the rollback and there is a new version installed in Linux already.
All that’s needed is an email address and a password (plus a passphrase known only to you). I’ve used Firefox sync ever since it began - never any issues - it keeps bookmarks and extensions in sync across my LAN and when multibooting each OS.
I created an email account especially for the sync, although it wasn’t necessary. Vivaldi also has a sync feature that does the same as Firefox.
Sometimes, caution can turn to paranoia. 
I don’t know if it will, but maybe this helps:
1 Like
Im actually copied and replaced all that recommend files that was listed in this Guide.
That Guide is sadly not worth it to read. 
Besides my bookmarks, nothing else changed.
Actually in Windows you can easily back and restore your full firefox profile and thats it. I saw it in a Youtube video… the problem relys to “Linux” Firefox and specially the rollback function that refused to load a current profiles with a older version. Even when i replace all files and overwrite the new profile files with my latest current profile, the profile won’t load.
Strange that no one rolled his Firefox Version back and faced all this problems yet.
FIX, How to handle a Firefox Rollback with your current Profile:
I found it out for myself, the problem that lead to that STUPID FIREFOX POP UP (from my screenshot above) was in my firefox profile and there was a file named:
compatibility.ini
This file use a version check and when we rollback Firefox under Linux
this versions need to be equal to the current firefox version or the Firefox Profile refused to load!
So i replaced this code from the file:
LastVersion=137.0_20250331232538/20250331232538
with my rolled back Firefox version under Linux:
LastVersion=136.0.4_20250327171315/20250327171315
And everything working as intended. Holy crap, this took me a few hours to found the damn issue… but i got it 
2 Likes
Please don’t mark my info as a solution, this topic will automatic closed itself soon
It was just a solution for the rollback workaround for Firefox 136.
The main error still isn’t fixed… firefox 137.0 won’t stream any video files.
Rollback to 136 just helps to skip some time, till anyone know how to fix this or hopefully mozilla is releasing a hotfix.
Im still not sure, if im alone with that bug… i would like some feedback if someone else face this issue.
Oops, I didn’t realise I did.
I recall clicking a “like” - perhaps I missed.
Cheers.
This prompted me to search the forum again. I found this topic:
It seems like it might be related.
A possible issue with pulse-audio and/or pipewire.
1 Like
no problem on librewolf here. (Firefox) base.
What is the journal-log says and the output while starting Firefox from the Terminal…
Well is your librewolf updated already with the newest base version from FF? The Firefox 137 was just rolled out yesterday or not?
I may report back in a few days, im just happy that i could FF136 running again.
Yeah i was checking this topic before i created this one here today.
Its strangely pretty close to my issue, but since the OP created it 16 days ago, it can’t be related to the new FF version 137… which i have problems with.
Another user also reported he had issues with all other browsers… but my FF 136.0.4 is running fine right now.
I also saw many pipewire/pulse audio issues in the stable release Topic, after they all did the update. But my system wasn’t affected after the stable update.
1 Like
I have a feeling it has to do with Firefox’s prefs.js file. If a major new feature is added/enabled, requiring the addition of new preference entries, then rolling back is not possible because the older version of Firefox won’t have any idea what the new preferences in the prefs.js file mean. Some preferences that the earlier version requires may also have been removed in the new version.
In this case, there were some big changes made to Firefox v137:
Tab groups begin rolling out today! Stay productive and organized with less effort by grouping related tabs together. One simple way to create a group is to drag a tab onto another, pause until you see a highlight, then drop to create the group. Groups can be named, color-coded, and are always saved. You can close a group and reopen it later.
Firefox Address Bar Refresh 2025 - new ways to search for things new, previously viewed, and more - all from the address bar:
I won’t list all of the address bar & search changes here - they can be viewed at the above link
And, most importantly for Linux users:
Support HEVC playback on Linux.
My view is that it is most likely the enabling of HEVC playback that is the cause @Kobold’s original issue. I can’t offer a fix for that - the first thing I do whenever Firefox updates is check the release notes, and I immediately went to an HEVC video test page to see if the new feature worked, and it did playback the HEVC video without any issues.
Maybe, when back on Firefox v137, @Kobold could open the about:support page, scroll down to the graphics section & see if HEVC is enabled in the Codec Support Information section:
Also, I would recommend using Firefox browser sync in future to preserve your Firefox data, and setting up & downloading an account recovery key to sign in to your Mozilla account to regain access to your data.
2 Likes
Me too: it has saved my bacon. Some years ago, it was the only way to get at my login credentials again following a hard disk crash or something (can’t remember the exact details) and regain access to the sites I use.
I shall, however, confirm that there are no apparent issues at my end since the switch to FF137. Videos play OK.
1 Like
Firefox 137.0 has no issues playing videos using a default installation.
When you are having issues, you should look into your settings - and from your comments above it is clear that you have altered the default configuration beyond recognition.
One or more of these alterations has made Firefox stop playing videos - which one(s) is impossible to know.
Using the messed up expression indicates it is a Firefox bug - but it is not - it is either parts of your configuration which is not compatible or it is simply the default view - which you don’t like - neither way is it a bug in Firefox.
1 Like
Same here. Well, that I know of anyway.
I should qualify here that the only “video” site I regularly use is, currently, YouTube.
There are, of course, a few YT alternatives which I haven’t yet tested (simply not the content there, at present, which I am interested in); neither have I checked the social media sites (e.g. Facebook, X) but I don’t use those either, generally.
Good point with HEVC support, i look for it when i try 137 again.
Maybe it is a nvidia card issue, that happen with my 2080ti possible there is
something going on between HEVC and my nvidia grub command,
that i used in the past for hardware codec support for firefox:
nvidia_drm.modeset=1
I have a feeling that HEVC maybe are forced on my GPU and that its maybe the reason why the video’s won’t be played.
Nvidia PC, FF 136:
Codec Name Software Decoding Hardware Decoding
H264 Supported Supported
VP9 Supported Supported
VP8 Supported Supported
AV1 Supported Unsupported
HEVC Unsupported Unsupported
AAC Supported Unsupported
MP3 Supported Unsupported
Opus Supported Unsupported
Vorbis Supported Unsupported
FLAC Supported Unsupported
Wave Supported Unsupported
Im using a dupplicated firefox profile on my AMD Laptop… i report back
if i have the same issue there too or not.
Update:
Video Playback is fine on FF137 with AMD Laptop and since the Firefox Profile are duplicated on both systems, its pretty sure there is something wrong around nvidia video codec support right now with FF137.
AMD Laptop, FF137:
Codec Name Software Decoding Hardware Decoding
H264 Supported Supported
VP9 Supported Supported
VP8 Supported Unsupported
AV1 Supported Unsupported
HEVC Supported Supported
AAC Supported Unsupported
MP3 Supported Unsupported
Opus Supported Unsupported
Vorbis Supported Unsupported
FLAC Supported Unsupported
Wave Supported Unsupported
Nvidia PC, FF 137 (Video’s not Playing 
):
Codec Name Software Decoding Hardware Decoding
H264 Supported Supported
VP9 Supported Supported
VP8 Supported Supported
AV1 Supported Unsupported
HEVC Supported Supported
AAC Supported Unsupported
MP3 Supported Unsupported
Opus Supported Unsupported
Vorbis Supported Unsupported
FLAC Supported Unsupported
Wave Supported Unsupported
Im already removed my nvidia grub command but still no success.
Terminal shows this error:
libva error: /usr/lib/dri/nvidia_drv_video.so init failed
I had installed libva-nvidia-driver in the past to gain Hardware Video Acceleration support.
I reverted to the default Software Decoding in about:config from
media.hardware-video-decoding.force-enabled = true
to (default)
media.hardware-video-decoding.force-enabled = false
And videos working again in FF 137 with my nvidia GPU but of course… no longer HW Video decoding.
Still better than nothing. 
Nvidia PC, FF 137 (Software Decoding only):
Codec Name Software Decoding Hardware Decoding
H264 Supported Unsupported
VP9 Supported Unsupported
VP8 Supported Unsupported
AV1 Supported Unsupported
HEVC Supported Unsupported
AAC Supported Unsupported
MP3 Supported Unsupported
Opus Supported Unsupported
Vorbis Supported Unsupported
FLAC Supported Unsupported
Wave Supported Unsupported
3 Likes
kudos for the troubleshooting - locating the setting causing your issue 
- and for letting us know how you solved It 