Ubuntu 24.04.3: Noble Numbat point release slips out quietly
(2025/08/08)
- Reference: 1754670314
- News link: https://www.theregister.co.uk/2025/08/08/ubuntu_24043_quietly_slips_out/
- Source link:
The latest point release of the current Ubuntu LTS is here, with a new kernel and a host of improvements for server and desktop alike.
The [1]Ubuntu 24.04.3 release includes a [2]substantial list of fixes. There are updates for the bootloader used on RISC-V hardware, better networking configuration in the early stages of the boot process, and updates to QEMU, lib-virt , and cloud-init .
It now has LibreOffice 24.8.7 and Firefox 141, and a new version of snapd, 2.68.5. There are multiple updates to GNOME, including to the Mutter window manager and compositor and the Nautilus file manager. Updates to Gtk4 improve the handling of Unicode emoji and integration with the Orca screen reader, and to the Pipewire audio server.
[3]
We're focusing on GNOME because that is the only official LTS desktop with the full lifespan. The various flavors with other desktops, such as Kubuntu, Lubuntu, Xubuntu and so on don't get the full five years of updates that the GNOME edition does. As an example, the [4]Kubuntu wiki page specifies that it only gets three years of updates. If you prefer one of the rapidly-changing desktops such as KDE Plasma or LXQt, you should consider running interim versions instead.
[5]
[6]
Ubuntu 24.04 "Noble Numbat" appeared in [7]late April last year , just a couple of weeks after a [8]delayed beta version . This appeared about two weeks late because of the [9]zx library backdoor in March 2024. Other delays have plagued the Noble release cycle. The [10]upgrade from the previous interim release was delayed, too. Then, in August, the [11]first point release was held back two weeks . Six months ago, there was a [12]one-week delay in the release of [13]version 24.04.2 .
According to the [14]company's own statement , about 95 per cent of Ubuntu users stick to the LTS releases. That means that the roughly semi-annual point releases to LTS versions serve two separate purposes: they're both update roll-ups, and they're also newer install media for the latest hardware.
[15]
The first of these means that each point release incorporates all the bug fixes and updates issued since the previous point release. So, if you installed an earlier point release and you've kept it updated since, then you don't need to do anything: you'll get the latest point release automatically.
The second purpose of the point-releases is different in two separate ways. Canonical makes new installation images available for each point release. The direct benefit of this is that, if you install a new machine or VM from these updated images, then it has all the updates up to that point pre-installed, meaning the first update will be a lot smaller and quicker.
The new version also refreshes the thousands of device drivers included with the OS. The design of the Linux kernel means that the bulk of the system's device drivers are part of the kernel itself; the main exception are graphics drivers, which come with the X.org X11 server. (This does not apply to Wayland, which uses the DRM drivers in the kernel.)
[16]
If you want to install the ageing LTS release on shiny new hardware that might be younger than the OS, and so contain hardware that's newer than the bundled drivers, Canonical bundles a new kernel and graphics subsystem. The company calls these [17]LTS Hardware Enablement Stacks , or HWE for short.
[18]Canonical dusts off TPM encryption for Ubuntu 25.10
[19]Ubuntu turns 20: 'Oracular Oriole' shows this old bird's still got plenty of flight
[20]Why we're still waiting for Canonical's immutable Ubuntu Core Desktop
[21]Gadget geeks aghast at guru's geriatric GPU
Each interim version of Ubuntu has a new kernel version, as you'd expect from a new version of the distro. But the first point release of an LTS arrives in August – before the next interim release. Those come out each October. As such, the first point release of an Ubuntu LTS has the latest build of the same kernel version with which it originally shipped. The HWE stack gets bundled from the second LTS point release onwards, when the OS and its drivers are over a year old.
So, in the the case of Noble, 24.04.1 came with kernel 6.8. Then 24.04.2 came with kernel 6.11 from [22]24.10 "Oracular Oriole" . Now, 24.04.3 comes with kernel 6.14 from [23]25.04 "Plucky Puffin" , plus version 25.0.7 of the Mesa 3D stack, including the new [24]Mesa Amber drivers for older GPUs.
If you installed from the original release of the LTS, then your hardware is presumably working and has been all along. That means that you don't need the new HWE stack. So, working on the principle of "if it ain't broke don't fix it," users of the original LTS version do not automatically receive the new kernel and graphics stack. If you want it, you must install it manually. Canonical's [25]kernel release cycle page has instructions.
As it happens, the FOSS desk upgraded his official Register issue laptop to Noble before it was officially available, so we were originally running 24.04 – point zero, so to speak. (As [26]point 9 of the upgrade guide says, it's as simple as doing update-manager -d .) So, this machine didn't automatically get the HWE stack when it received the rest of 24.04.3. For this article, we grabbed the latest one with the following command: sudo apt-get install --install-recommends linux-generic-hwe-24.04
We are happy to report that we are now on kernel 6.14, and the system works exactly as it did before. ®
Get our [27]Tech Resources
[1] https://fridge.ubuntu.com/2025/08/08/ubuntu-24-04-3-lts-released/
[2] https://discourse.ubuntu.com/t/noble-numbat-point-release-changes/47565/4
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://wiki.ubuntu.com/NobleNumbat/ReleaseNotes/Kubuntu
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://www.theregister.com/2024/04/29/ubuntu_2404_fed_40_et_al/
[8] https://www.theregister.com/2024/04/15/ubuntu_24_04_belated_beta/
[9] https://www.theregister.com/2024/03/29/malicious_backdoor_xz/
[10] https://www.theregister.com/2024/05/24/ubuntu_2404_upgrades_available/
[11] https://www.theregister.com/2024/08/19/ubuntu_240401_will_be_late/
[12] https://lists.ubuntu.com/archives/ubuntu-release/2025-February/006310.html
[13] https://lists.ubuntu.com/archives/ubuntu-announce/2025-February/000308.html
[14] https://ubuntu.com/about/release-cycle
[15] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[16] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[17] https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[18] https://www.theregister.com/2025/07/31/ubuntu_tpm_fde/
[19] https://www.theregister.com/2024/10/11/ubuntu_oracular_oriole_released/
[20] https://www.theregister.com/2024/11/06/ubuntu_core_desktop_waiting/
[21] https://www.theregister.com/2025/08/01/geeks_aghast_at_guru_gpu/
[22] https://www.theregister.com/2024/10/11/ubuntu_oracular_oriole_released/
[23] https://www.theregister.com/2025/04/24/ubuntu_fedora_spring/
[24] https://docs.mesa3d.org/amber.html
[25] https://ubuntu.com/kernel/lifecycle
[26] https://help.ubuntu.com/community/NobleUpgrades/
[27] https://whitepapers.theregister.com/
The [1]Ubuntu 24.04.3 release includes a [2]substantial list of fixes. There are updates for the bootloader used on RISC-V hardware, better networking configuration in the early stages of the boot process, and updates to QEMU, lib-virt , and cloud-init .
It now has LibreOffice 24.8.7 and Firefox 141, and a new version of snapd, 2.68.5. There are multiple updates to GNOME, including to the Mutter window manager and compositor and the Nautilus file manager. Updates to Gtk4 improve the handling of Unicode emoji and integration with the Orca screen reader, and to the Pipewire audio server.
[3]
We're focusing on GNOME because that is the only official LTS desktop with the full lifespan. The various flavors with other desktops, such as Kubuntu, Lubuntu, Xubuntu and so on don't get the full five years of updates that the GNOME edition does. As an example, the [4]Kubuntu wiki page specifies that it only gets three years of updates. If you prefer one of the rapidly-changing desktops such as KDE Plasma or LXQt, you should consider running interim versions instead.
[5]
[6]
Ubuntu 24.04 "Noble Numbat" appeared in [7]late April last year , just a couple of weeks after a [8]delayed beta version . This appeared about two weeks late because of the [9]zx library backdoor in March 2024. Other delays have plagued the Noble release cycle. The [10]upgrade from the previous interim release was delayed, too. Then, in August, the [11]first point release was held back two weeks . Six months ago, there was a [12]one-week delay in the release of [13]version 24.04.2 .
According to the [14]company's own statement , about 95 per cent of Ubuntu users stick to the LTS releases. That means that the roughly semi-annual point releases to LTS versions serve two separate purposes: they're both update roll-ups, and they're also newer install media for the latest hardware.
[15]
The first of these means that each point release incorporates all the bug fixes and updates issued since the previous point release. So, if you installed an earlier point release and you've kept it updated since, then you don't need to do anything: you'll get the latest point release automatically.
The second purpose of the point-releases is different in two separate ways. Canonical makes new installation images available for each point release. The direct benefit of this is that, if you install a new machine or VM from these updated images, then it has all the updates up to that point pre-installed, meaning the first update will be a lot smaller and quicker.
The new version also refreshes the thousands of device drivers included with the OS. The design of the Linux kernel means that the bulk of the system's device drivers are part of the kernel itself; the main exception are graphics drivers, which come with the X.org X11 server. (This does not apply to Wayland, which uses the DRM drivers in the kernel.)
[16]
If you want to install the ageing LTS release on shiny new hardware that might be younger than the OS, and so contain hardware that's newer than the bundled drivers, Canonical bundles a new kernel and graphics subsystem. The company calls these [17]LTS Hardware Enablement Stacks , or HWE for short.
[18]Canonical dusts off TPM encryption for Ubuntu 25.10
[19]Ubuntu turns 20: 'Oracular Oriole' shows this old bird's still got plenty of flight
[20]Why we're still waiting for Canonical's immutable Ubuntu Core Desktop
[21]Gadget geeks aghast at guru's geriatric GPU
Each interim version of Ubuntu has a new kernel version, as you'd expect from a new version of the distro. But the first point release of an LTS arrives in August – before the next interim release. Those come out each October. As such, the first point release of an Ubuntu LTS has the latest build of the same kernel version with which it originally shipped. The HWE stack gets bundled from the second LTS point release onwards, when the OS and its drivers are over a year old.
So, in the the case of Noble, 24.04.1 came with kernel 6.8. Then 24.04.2 came with kernel 6.11 from [22]24.10 "Oracular Oriole" . Now, 24.04.3 comes with kernel 6.14 from [23]25.04 "Plucky Puffin" , plus version 25.0.7 of the Mesa 3D stack, including the new [24]Mesa Amber drivers for older GPUs.
If you installed from the original release of the LTS, then your hardware is presumably working and has been all along. That means that you don't need the new HWE stack. So, working on the principle of "if it ain't broke don't fix it," users of the original LTS version do not automatically receive the new kernel and graphics stack. If you want it, you must install it manually. Canonical's [25]kernel release cycle page has instructions.
As it happens, the FOSS desk upgraded his official Register issue laptop to Noble before it was officially available, so we were originally running 24.04 – point zero, so to speak. (As [26]point 9 of the upgrade guide says, it's as simple as doing update-manager -d .) So, this machine didn't automatically get the HWE stack when it received the rest of 24.04.3. For this article, we grabbed the latest one with the following command: sudo apt-get install --install-recommends linux-generic-hwe-24.04
We are happy to report that we are now on kernel 6.14, and the system works exactly as it did before. ®
Get our [27]Tech Resources
[1] https://fridge.ubuntu.com/2025/08/08/ubuntu-24-04-3-lts-released/
[2] https://discourse.ubuntu.com/t/noble-numbat-point-release-changes/47565/4
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://wiki.ubuntu.com/NobleNumbat/ReleaseNotes/Kubuntu
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://www.theregister.com/2024/04/29/ubuntu_2404_fed_40_et_al/
[8] https://www.theregister.com/2024/04/15/ubuntu_24_04_belated_beta/
[9] https://www.theregister.com/2024/03/29/malicious_backdoor_xz/
[10] https://www.theregister.com/2024/05/24/ubuntu_2404_upgrades_available/
[11] https://www.theregister.com/2024/08/19/ubuntu_240401_will_be_late/
[12] https://lists.ubuntu.com/archives/ubuntu-release/2025-February/006310.html
[13] https://lists.ubuntu.com/archives/ubuntu-announce/2025-February/000308.html
[14] https://ubuntu.com/about/release-cycle
[15] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[16] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aJZzd0QhL9a1kkOpVVZBtgAAAAE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[17] https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[18] https://www.theregister.com/2025/07/31/ubuntu_tpm_fde/
[19] https://www.theregister.com/2024/10/11/ubuntu_oracular_oriole_released/
[20] https://www.theregister.com/2024/11/06/ubuntu_core_desktop_waiting/
[21] https://www.theregister.com/2025/08/01/geeks_aghast_at_guru_gpu/
[22] https://www.theregister.com/2024/10/11/ubuntu_oracular_oriole_released/
[23] https://www.theregister.com/2025/04/24/ubuntu_fedora_spring/
[24] https://docs.mesa3d.org/amber.html
[25] https://ubuntu.com/kernel/lifecycle
[26] https://help.ubuntu.com/community/NobleUpgrades/
[27] https://whitepapers.theregister.com/
Re: hoping they backport critical ZFS memory leak fix(at some point..)
Liam Proven
> hoping they backport critical ZFS memory leak fix
Ouch. Nasty.
https://packages.ubuntu.com/noble/zfsutils-linux
-- still on 2.2.
The only way to get newer would be to play Klara, or compile from source. I have done the latter on a RasPi 4 on Ubuntu Server 20.04 and it worked. Took an hour or so but it was doable.
What's in a name
frankvw
While Ubuntu and its derivatives (especially Mint) continue to delight me and keep me productive, I have to wonder about Ubuntu's release names. Fecal Fossil, Noble Numbnuts... Who's making that stuff up?
Re: What's in a name
Liam Proven
> Who's making that stuff up?
TBH I have long harboured a slight suspicion that it is Shuttleworth's main contribution in recent years. ;-)
I am OK with version numbers but many people find names easier, and release names are a deeply-seated assumption in Debian package management.
hoping they backport critical ZFS memory leak fix(at some point..)
Started deploying Ubuntu 24 about a year ago and I have been using ZFS on my Splunk systems mainly to assist in backups with custom ZFS replication scripts. But quickly found massive memory leaks somewhere, and traced it to ZFS. Which made ZFS unusable for my Splunk systems unless I wanted to allocate 10s of gigabytes of memory (or for production over 100GB) to get Splunk to run as ZFS was blowing the doors off the ARC cache limit. Lots of others reported the same issue(with other workloads) though specifically on ZFS 2.3, I found it on 2.2 which is included with Ubuntu 24.04. I have ZFS 2.2 on Ubuntu 24 deployed for a couple of other workloads and it works fine for them. Seems just workloads that need to open a lot of files trigger the leak. My wild guess is perhaps this leak was introduced with https://github.com/openzfs/zfs/pull/14359 (but that is based only on I couldn't find anything else that looked more likely specifically regarding eviction logic, and this change was part of 2.2 not 2.3).
https://github.com/openzfs/zfs/issues/17052
Some think they found the fix to the issue in https://github.com/openzfs/zfs/pull/17542 . I'm not in any rush to test a fix myself(assuming it works..) as I have a working solution with Ubuntu 22.04 Linux kernel 5.15 with ZFS 2.1 working just fine on Ubuntu 24 for my Splunk systems. I saw a request to backport the fix to ZFS 2.2, but haven't noticed whether that has actually happened yet or not.
I recall after upgrading to Ubuntu 20 from 16(which was a complete system replacement of each server rather than an "upgrade") running into a nasty BIND bug which wrecked havoc on my DNS for half a year until I finally figured out what was causing it (https://kb.isc.org/docs/aa-01315), turns out someone had reported the bug to Ubuntu already but it sat unfixed for who knows how long(months at least by the time I noticed what to look for and saw the bug was already filed, didn't later track down when/if it actually got fixed(by setting the option) or if it was fixed later automatically by a newer version of BIND) ... I have kept prefetch disabled to this day (DNS ran fine for decades without it, so... don't really need it now)
Fortunately this ZFS issue reared it's head immediately and I was able to find a suitable workaround.