I believe the patch referenced above causes other bad behaviors.
Specifically, it causes systemd-networkd to be restarted without any sort of prompt whenever a library it links with receives a security update. In my experience restarting systemd-networkd can break active WireGuard tunnels and can cause chronyd to stop polling IPv6 servers.
I think the change at issue is adding the flags "-m u" to apt-pinvoke in /etc/apt/apt.conf.d/99needrestart, which also means needrestart now ignores a setting of "NEEDRESTART_MODE=l" in the environment when run from apt.
I've started to add systemd-networkd to my needrestart ignore list, but perhaps that should be a default setting, as it is for NetworkManager.
I'm testing with Noble in a LXD VM with an image from the ubuntu-daily repository.
I believe the patch referenced above causes other bad behaviors.
Specifically, it causes systemd-networkd to be restarted without any sort of prompt whenever a library it links with receives a security update. In my experience restarting systemd-networkd can break active WireGuard tunnels and can cause chronyd to stop polling IPv6 servers.
I think the change at issue is adding the flags "-m u" to apt-pinvoke in /etc/apt/ apt.conf. d/99needrestart , which also means needrestart now ignores a setting of "NEEDRESTART_ MODE=l" in the environment when run from apt.
I've started to add systemd-networkd to my needrestart ignore list, but perhaps that should be a default setting, as it is for NetworkManager.
I'm testing with Noble in a LXD VM with an image from the ubuntu-daily repository.
Thanks.