|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
This just appeared today in my LMC 20 Update Manager. I’ve already got Firefox 135.0.1 installed. Is anyone else getting this? I’m just guessing that it might be the Firefox “Terms & Conditions” rebuild. I haven’t seen anything mentioned anywhere about it on Google, etc.
Nothing new on Mozilla’s FTP site for 135.0.1 in the Linux directories. Everything there’s dated February 18th, even the stuff in the “update” folder which contains update files to go from the immediately prior versions to 135.0.1. The files are in a .mar format which, I believe, Firefox’s built-in updater uses.
Perhaps you’re right, @Charlie, in that the other file that’s included in your screenshot is an updated EULA for FF disguised as a “rebuild” of 135.0.1.
I’m seeing this, too. Don’t know what it means. Haven’t installed it yet.
The “rebuild” part for 135.0.1 is most likely due to it being repackaged as an emergency update to include older discontinued releases per the Linux Mint blog
Important Firefox Update
On March 14, 2025, a root certificate used by Firefox will expire.
When this happen, Firefox version 128 (and lower) will suffer significant issues related to:
- configuration
- add-ons
- signed content
- DRM-protected media playback
To avoid these problems, make sure you’re up to date in your Update Manager. Press Refresh and apply all updates.
This is important for security reasons, and in this case it’s also important to avoid regressions.
Firefox 135.0.1 is available on all supported Linux Mint releases.
Firefox 135.0.1 was also sent as an emergency update to the following discontinued releases:
- Linux Mint 19.3, 19.2, 19.1 and 19
- LMDE 5
- LMDE 4
If you are using a discontinued version of Linux Mint (20 or older) or LMDE (5 or older) please upgrade or reinstall Linux Mint.
I am getting ready to update to LMC version 22 soon. It’s my understanding that I have until April to update although I haven’t seen it said anywhere exactly when in April. At any rate, I plan to be updated to 22 sometime in March.
Meanwhile. I’m getting nagged with the following everyday:
I never got this nag on Linux Mint 19.
In your screenshot it says “It will stop receiving support and updates in 88 days”. So that appears to be the end of May 2025.
To stop seeing that notice, go to Startup Applications, then click the slider to the right of System Reports to disable it from starting when you boot up or log into the computer. Or at the top, try right clicking on “Your version of Linux Mint will soon reach End-of-Life (EOL)” and see if there is an option to ignore or dismiss it.
It isn’t really that bad, a little icon appears in the systray. If I left click on it I get that System Reports message, but I can just right click on the icon and click on quit to turn it off. It is weird though that the message is counting down the days from 89 (when it started) to the EOS.
I got out my old Sony laptop with LMC 19.1 and checked for updates and there were two, one of them being the Firefox 135.0.1 update. So I ran them both and the new Firefox works fine. I wasn’t expecting that but am glad to have an up to date Firefox just in case I should need to use the old Sony.
The rebuild did not come from Mozilla, but from Linux Mint due to their decision to send 135.0.1 as an emergency update to discontinued releases (see my post above). This caused all Firefox 135.0.1 packages to be updated in the Linux Mint repository which is then picked up and displayed in Update Manager when it queries the repository for updates.
Note: on the repository webpage, click the “Last modified” at the top to sort by most recent date and see all the Firefox 135.0.1 packages that have been updated (rebuilt) Feb. 28.
Okay, what I have now is working fine but I guess I’ll make another Timeshift restore point and then do the newer update (135.0.1+linuxmint2+una). I don’t have Una, I have Ulyana. Once again I guess I have to force myself to trust the Update Manager. Thanks again.
In my experience it’s a lot better to trust the Mint Update Manager than to, for example, trust Windows Update. I can’t remember a time when Update Manager screwed something up, and I’ve been using it in either Mint or Ubuntu for nearly 8 years. That’s in direct contrast to my getting an error from Windows Update just last night when I was trying to install the February CU on a Win 10 machine. The error said something went wrong and we can’t install the update. WU did try again later and failed again. I don’t have time for nonsense like that.
It has “una” listed at the end as the Firefox package (and many other packages) use the name of the last release of the series (20.x is Ulyana, Uma and Una). Same for the other release versions, where 21.x uses Virginia (first two names were Vera and Victoria) and 22.x currently uses Xia.
However at this point, another option would be to wait for Firefox 136 that Mozilla officially releases tomorrow (it’s already on their FTP site) and then Linux Mint will package it and publish it to their repository usually a few days later where it will then be available in Update Manager.
Be careful with 136 and be sure to read the topic Firefox 136 AI invasion. If it wasn’t for all the security fixes and patches, I wouldn’t bother with it.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
