Linux distribution: Release of Ubuntu 24.04.1 delayed
Canonical has postponed the release of the first point release for the current LTS version by two weeks: There are still a few open issues.
(Image: Canonical)
The point release 24.04.1 for Ubuntu's current LTS release 24.04 comes two weeks later than originally planned. The reason for this are various bugs that still need to be ironed out.
This is according to a recent Discourse article. The main problem is five upgrade blockers, i.e. bugs that need to be fixed before an update can take place.
The entry lists the following open problems in detail:
- #2076324: snapd support code for nvidia is out of date and causess regression on 550-era drivers
- #2075337: [SRU] py3clean fails when using alternate character set
- #2043820: Unable to contact snap store on Xubuntu from Jammy to Noble
- #2075968: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04
- #2074309: upgrade 22.04 -> 24.04 won't start due to feature flags
The targeted release date for version 24.04.1 LTS is now August 29.
Secure boot issue
As soon as Canonical provides setup media for the point release, the boot loader should in the best case also be updated to fix an annoying problem: Microsoft distributed an SBAT (Secure Boot Advanced Targeting) update with the August patches for Windows 10 and 11 on August 13, which causes some current Linux setup media to fail to boot due to an outdated boot loader.
Anyone who currently wants to boot an Ubuntu setup stick on an up-to-date Windows PC must use a workaround for the time being. By far the simplest: disable Secure Boot. But be careful: If the Windows installation is encrypted with BitLocker or its slimmed-down variant "Device Encryption", disabling Secure Boot can in some cases trigger a request for the recovery key. You should make a note of this before switching off Secure Boot so that you have it to hand if necessary. It can be displayed in a terminal with admin rights and the command manage-bde -protectors -get c:. The 48-digit number string that the command returns as a "numeric password" is the recovery key.
(jss)
