Comment 16 for bug 2054761

I have verified the fix using systemd 255.4-1ubuntu8.1 from noble-proposed. On a Jammy Desktop system, I simply ran an upgrade:

nr@clean-jammy-amd64:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-22 11:45:16-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.82, 185.125.190.36, 91.189.91.83, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: \u2018noble.tar.gz\u2019

noble.tar.gz 100%[===================>] 1.21M --.-KB/s in 0.1s

2024-05-22 11:45:16 (9.20 MB/s) - \u2018noble.tar.gz\u2019 saved [1274850/1274850]

nr@clean-jammy-amd64:~$ tar xf noble.tar.gz
nr@clean-jammy-amd64:~$ sudo -E ./noble --frontend DistUpgradeViewNonInteractive
[ ... ]

The upgrade proceeded without issue. Namely, my session was not killed during the upgrade.

nr@clean-jammy-amd64:~$ apt policy systemd
systemd:
  Installed: 255.4-1ubuntu8.1
  Candidate: 255.4-1ubuntu8.1
  Version table:
 *** 255.4-1ubuntu8.1 500
        500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     255.4-1ubuntu8 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages