Snapd 2.73 Release Update

snapd
1

Dear Snapd Community,

We’re pleased to share that snapd 2.73 snap is available for testing in the candidate channel. Snapd 2.73 is scheduled for release to the stable channel on 6 January 2026. This will be followed by the release of the snapd 2.73 Debian packages to Jammy, Noble, Plucky, Questing, and Resolute.

Overview

Snapd 2.73 does not introduce new user-facing features. Instead, it provides:

  • Bug fixes and robustness improvements
  • Interface additions supporting new and emerging use cases
  • Building blocks for several work-in-progress features, including:

These changes are intended to improve reliability today while preparing the ground for upcoming releases.

Notable updates

  • FDE: On Ubuntu Core systems using UEFI ≥ 2.5, when Deployed Mode is disabled, both AuditMode and DeployedMode are now measured and must be permitted to ensure that autorepair continues to function correctly.
  • Fix scenario where multiple snaps refreshed together skips refresh control
  • Prevent disabling base snaps to ensure dependent snaps can be removed
  • Protect the per-snap tmp directory against being reaped by age
  • Avoid race between store download stream and cache cleanup executing in parallel when invoked by snap download
  • Use “current” instead of revision number for icons (LP: #1851490)
  • Add snapctl version command (LP: #2121853)
  • Ensure no more than one partition on disk can match a gadget partition (LP: #2127214)
  • Prompting: Do not record notices for unchanged rules on snapd startup (LP: #2127189)
  • snap-confine: Update AppArmor profile to allow read/write to journal as workaround for snap-confine fd inheritance prevented by newer AppArmor (LP: #2127244)

For the release plan and complete list of changes, please refer to the full release notes. For an overview on TPM backed FDE for hybrid Ubuntu 25.10, see: TPM/FDE progress for Ubuntu 25.10

Test Feedback

Feel free to provide your test feedback here or directly in Launchpad. To help fast track investigations please provide (1) details about the system, (2) snapd version(s) and (3) steps to reproduce the issue.

What’s next

The next release, Snapd 2.74, is estimated to start on 12 January 2026 and be available by 6 March 2026, and will be used in the 26.04 installation image that will deliver an early version of TPM backed Full Disk Encryption for Classic Hybrid systems (Classic Ubuntu with Kernel and Gadget snaps).

We greatly appreciate your contributions and support!

1 Like
3

Progressive release of snapd 2.73 snap from candidate to stable is now in progress.

4

Snapd 2.73 deb packages have now been released to Jammy, Noble, Plucky, and Questing. The release was already available in Resolute.

5

Hi @ernestl

I have some test systems where we add an extra key signature to the SB signature DB, in order to load some extra custom signed kernel modules.

It appears that snapd 2.73 is preventing them the system install routing from working properly now. The install mode seems to work ok, but on first run mode the recovery key is requested [ which of course we don’t have at that point ].

I seems likely it may be related to the quoted change.

It worked fine with snapd 2.72

Is this new behaviour expected ? Is there any extra configuration needed with such a setup now to make it work ?

Thanks!

Cheers.

Just