Yesterday, pamac proposed an upgrade to firefox 142 and I did it. Today, it is complaining that my local firefox is newer than the one in the repos. Was the firefox 142 package removed? Is there a reason for it? Can one safely stay on the removed package? Unfortunately, reinstalling 141.0.3 will lead to a firefox version that refuses to work with the current profile, that had been modified by running 142.
Same here. Thatās also the upgrade that causes the issue Iād described here as well as an occasional rare stutter at left clicks at ānormalā mouse use.
1 Like
Firefox is usually released to all branches simultaneously
If the new version of Firefox is working OK, warning can be ignored
1 Like
firefox --allow-downgrade
If you downgrade Firefox, you also have to restore compatibility.ini file from 141.0.3.
If you donāt have a backup, itās a text file, somebody can copy&paste the content here and you copy it inside your compatibility.ini file.
An example:
2 Likes
There was a problem with the firefox package. Just use whatever works for you for now (depending on branch it might be the one or the other version), until @Yochanan takes care of it.
From a slightly earlier Firefox version (in case itās useful):
[Compatibility]
LastVersion=141.0_20250721102543/20250721102543
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox/browser
The file usually lives in the root directory of your Firefox profile.
2 Likes
Same problem here. ^^ā
I feel all your pain. I tried to upgrade to 142 but it froze my system. I unfroze it doing a tty and htop to kill it. Then I tried to downgrade it, which I thought worked until when I ran FF again it wanted to created a new profile. I said NO WAY and reversed the downgrade. After that FF 142 worked again. WTF? But all the while I had been using Falkon as my go to browser which works just great btw. Tkank you KDE for Falkon!!!
$ grep firefox /var/log/pacman.log
[2025-08-14T17:33:44+0100] [ALPM] upgraded firefox (141.0-1 -> 141.0.3-1)
[2025-08-14T17:33:44+0100] [ALPM] upgraded firefox-i18n-en-gb (141.0-1 -> 141.0.3-1)
[2025-08-21T10:26:01+0100] [ALPM] upgraded firefox (141.0.3-1 -> 142.0-1)
[2025-08-21T10:26:01+0100] [ALPM] upgraded firefox-i18n-en-gb (141.0.3-1 -> 142.0-1)
Anyone having problems with latest version of Firefox should check out Firefox troubleshooting tools
firefox --new-window about:support
Or
firefox --new-window about:profiles
to manage profiles
2 Likes
Hello.
In my case, it had remained working normally, but I didnāt tell you after I mentioned pamac that it was in a version but new and run sudo pacman -Syuu, returning to its old version, as I have it all in the cloud, I just connected it from new to my account and had it all configured again.
Yes. @philm pulled it for now.
Iāll see if I can actually rebuild Firefox for the stable branch sometime tomorrow:
Iāve just found 141.0.3 compatibility.ini as it was one week ago. 
[Compatibility]
LastVersion=141.0.3_20250807161057/20250807161057
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox/browser
1 Like
I had a similar topic identified where pacman told me the installed version (142.0-1) is newer than the version in repo (141.0.3-1)
I used pacman -Syuu exceptionally (note the second āuā, which allows downgrade) and downgraded the version to the one in repo.
I was not requested to update the ini file. Firefox worked flawless. It only told me that i started it the last time a while ago and it wantās to reset to defaults. But all tabs and bookmarks were restored after that.
No, you wouldnāt have been; that is, if you would expect Firefox or the Manjaro system to ask for it. The suggestion was offered as part of a possible workaround - though I am unfamiliar with its value, in practice.
1 Like
Thanks for clarifying! 142 seems to be working fine here, so I mainly wanted to know if it was pulled e.g. for some security reason or bug that could cause issues to the rest of the system.
1 Like
2 Likes
Thanks, just installed without issues
The installation went well, but Iām missing the language packs. These are currently only available for version 141.0.3-1.
1 Like
ā¦now available as of several hours ago. Sorry, forgot to push the matching 142.0-0.1 language packages earlier. 
2 Likes