I have done manual tests with jammy-proposed and focal-proposed.
I have added in /etc/systemd/system, the following service and enabled it. Then rebooted.
```
[Unit]
DefaultDependencies=no
Before=systemd-udev-trigger.service
If the bug was present, it would not complete the boot and have filesystems unmounted. When the fix is working, the boot would complete and it is possible to ssh to it.
Results of the test:
Ubuntu Core 22
Without jammy-proposed: systemd 249.11-0ubuntu3.11 -> broken
With jammy-proposed: systemd 249.11-0ubuntu3.12 -> fixed
Ubuntu Core 20, with pc-kernel 22/beta
Without focal-proposed: systemd 245.4-4ubuntu3.22 -> broken
With focal-proposed: systemd 245.4-4ubuntu3.23 -> fixed
So I confirm the systemd packages in jammy-proposed and focal-proposed are fixing this issue.
I have done manual tests with jammy-proposed and focal-proposed.
I have added in /etc/systemd/ system, the following service and enabled it. Then rebooted. cies=no systemd- udev-trigger. service
```
[Unit]
DefaultDependen
Before=
[Service]
Type=oneshot
ExecStart=systemctl daemon-reload
[Install] multi-user. target
WantedBy=
```
If the bug was present, it would not complete the boot and have filesystems unmounted. When the fix is working, the boot would complete and it is possible to ssh to it.
Results of the test:
Ubuntu Core 22
Without jammy-proposed: systemd 249.11-0ubuntu3.11 -> broken
With jammy-proposed: systemd 249.11-0ubuntu3.12 -> fixed
Ubuntu Core 20, with pc-kernel 22/beta
Without focal-proposed: systemd 245.4-4ubuntu3.22 -> broken
With focal-proposed: systemd 245.4-4ubuntu3.23 -> fixed
So I confirm the systemd packages in jammy-proposed and focal-proposed are fixing this issue.