Linux Mint published its July 2026 monthly news, and two changes in it are worth a sysadmin's attention. Kernel management has moved out of Update Manager into the System Administration tool, and the model changed with the move: you now follow a kernel series rather than picking individual kernels, you say how many old ones to keep, and outdated kernels are removed automatically once a week with a history view showing what went and when. The same tool gained a page for setting environment variables system wide, for graphical sessions, console sessions or both. New hardware enablement ISOs shipped alongside, carrying kernel 7.0 for Mint 22.3.
The short answer
The Linux Mint July 2026 monthly news moved kernel management out of Update Manager and into the System Administration tool, which also brings it to LMDE. The model changed with the move: you follow a kernel series rather than choosing individual kernels, you set how many old ones to keep, and outdated kernels are removed automatically once a week, with a manual option and a history button showing what was removed and when. The same tool gained a page for setting environment variables system wide across graphical sessions, console sessions or both. New hardware enablement ISOs ship kernel 7.0 for Linux Mint 22.3.
Every Linux administrator has met a full /boot partition, and almost nobody has met it at a convenient time. It shows up when a kernel upgrade cannot write its initramfs, the package transaction stops half done, and the machine is now in a state where the next reboot is a question rather than a routine.
Linux Mint has spent this cycle building the tool that stops that happening, and the July 2026 monthly news, published on August 10, describes what it looks like.
Kernel management left Update Manager
The functionality moved into the System Administration tool, and the move brought it to LMDE as well as the Ubuntu based editions, which is more than a relocation.
The model changed too. Instead of a list of individual kernels where you pick one and then face the same choice at every point release, you now designate a kernel series to follow. Updates inside that series arrive through Update Manager like any other package. You set how many older kernels to retain, and outdated ones are removed automatically once a week, with a manual cleanup available if you would rather do it yourself and a history button that shows what was removed and when it went.
That history view is the part we would have asked for. Automatic deletion of boot artefacts is the sort of convenience that becomes uncomfortable the first time a machine will not boot and you want to know exactly what the system took away from you last Tuesday.
Why the retention count is the setting that matters
Keep too few kernels and you have no fallback. Keep too many and you are back at a full partition.
The arithmetic is unforgiving because /boot is usually small. Distributions have historically carved out 512 MB or 1 GB, and a single kernel entry costs you a vmlinuz image, a System.map and an initramfs that can exceed 100 MB once your hardware needs firmware. Four or five kernels is enough to fill it.
Two retained kernels is the setting we would use on a workstation: the running one and the previous one, which is what a fallback is actually for. Three has an argument on hardware where you have already been bitten by a regression and want more room to walk backwards. More than that is collecting, not planning.
If you are doing this by hand on other distributions, df -h /boot tells you where you stand and sudo apt autoremove --purge clears what the package manager already considers obsolete. That is the operation Mint is now scheduling for you.
The environment variables page is quietly the better feature
Setting a variable for every session on a Linux machine has never been one thing. It has been three or four, and which one is correct depends on a distinction most people only learn by getting it wrong.
/etc/environment is read by PAM and applies broadly, but it is not a shell script. It takes plain key equals value lines and nothing else: no expansion, no conditionals, no referring to another variable. Files dropped into /etc/profile.d/ are shell scripts and can do all of that, but they are sourced for login shells, which is not the same set of processes.
Graphical sessions are where this reliably goes wrong. A display manager may never source your profile, so a variable that is plainly present in a terminal is simply absent inside a desktop application launched from a menu, and the resulting bug report reads like nonsense until you know why.
Mint's new page lets you set a variable for graphical sessions, console sessions or both, which is the distinction that actually matters and the one the underlying files express badly. It does not remove the need to understand what is happening underneath, and we would still want to know which file a given setting landed in, but presenting the choice in those terms is the right framing.
The rest of the release
New hardware enablement ISOs are available for Linux Mint 22.3 carrying kernel 7.0, which is the usual route for getting recent hardware working on a long term support base.
Cinnamon gained Fcitx5 support with full Wayland and X11 parity, which matters for anyone typing Chinese, Japanese, Korean or an Indic script, since input methods have been one of the slower parts of the Wayland transition to reach parity. A new keyboard layout viewer replaces the discontinued gnome-kbd one. Panel behaviour around fullscreen windows was improved.
The project also reported June donations of 14,761 dollars from 419 donors, plus 2,353 patrons contributing 5,318 dollars a month.
What we would do
If you run Mint on more than one machine, set the retention count deliberately rather than accepting whatever is default, and set it the same everywhere. Fleet consistency is the entire value of a policy setting.
If you have been fighting a variable that works in a terminal and not in a desktop application, this page is the fix, and the reason it was broken is the login shell distinction rather than anything you did wrong.
And if you are still deciding where a machine belongs, our framework for choosing a Linux distribution in 2026 works through the long term support and rolling release trade in more detail than a release note can.
Sources and further reading
- Monthly News, July 2026, The Linux Mint Blog
- Linux Mint improves kernel management and setting system wide environment variables, Phoronix, August 10, 2026
- The Linux Mint project
Frequently asked questions
Why does a full /boot partition matter enough to build a tool around it?
Because it fails at the worst possible moment and it fails quietly. Each kernel install writes a vmlinuz image, an initramfs and a System.map into /boot, and an initramfs alone can run to 100 MB or more once your hardware needs a few firmware blobs. Distributions have historically sized /boot at 512 MB or 1 GB, so four or five kernels fill it. The failure mode is not a warning: the next kernel upgrade cannot write its initramfs, the package manager leaves the transaction half finished, and you find out at the next reboot. Automating removal on a schedule turns a latent outage into a background job, which is the correct treatment.
What changes when you track a kernel series instead of individual kernels?
It changes what you have to decide. Under the old model you were shown a list of individual kernels and picked one, which meant every point release put the choice in front of you again and made a fleet drift as different machines took different versions. Under the series model you state that a machine follows 7.0, and updates within that series arrive through Update Manager the way any other package does. You are choosing a policy once rather than making a decision repeatedly. The trade is that you have to be deliberate about moving between series, because that step is now explicit rather than something you can drift into.
How were system wide environment variables set before this page existed?
With several files that each cover a different case, which is exactly why a page for it is useful. `/etc/environment` is read by PAM and applies broadly, but it is not a shell script, so it takes plain key equals value lines and nothing else, no expansion and no conditionals. Files under `/etc/profile.d/` are shell scripts sourced at login, so they can do more but only for login shells. Graphical sessions are the awkward case, because a display manager may not source your profile at all, which is why a variable you set correctly for a terminal turns out to be missing inside a desktop application. The new page exists to cover graphical sessions, console sessions or both without you having to remember which file does which.
Does this apply to LMDE as well as Linux Mint?
Yes, and that is one of the more useful details in the announcement. Kernel management previously lived in Update Manager in a form specific to the Ubuntu based editions. Moving it into the System Administration tool made it work for LMDE, the Debian based edition, too. If you keep an LMDE machine as an insurance policy against upstream changes, which is the whole reason LMDE exists, it now gets the same kernel retention behaviour rather than a different one you have to remember separately.
What is Fcitx5 support in Cinnamon actually for?
Text input for languages that need an input method engine rather than a direct keymap, which is most of Chinese, Japanese and Korean plus a good number of Indic scripts. Fcitx5 is one of the two mainstream frameworks for that on Linux. The detail that matters here is full Wayland and X11 parity, because input methods have been one of the more persistent rough edges in the move to Wayland, and parity means users do not have to pick their session type based on whether they can type their own language. Cinnamon also gained a keyboard layout viewer to replace the discontinued gnome-kbd one.