Comment 22 for bug 2043820

I just tried an upgrade on Xubuntu from Jammy to Noble. The reason this happens is that in Kinetic, systemd-resolved was split into its own binary package, and at the time that the transitional deb(s) are being installed for thunderbird or firefox etc. (and hence the snap store connectivity check happens), systemd-resolved has not been installed yet. In other words, we have the following order of events:

1. New systemd unpacked / installed (results in systemd-resolved.service being killed and removed)
2. Snap transitional packages installed, snap store connectivity check attempted
3. New systemd-resolved unpacked / installed (systemd-resolved.service restored)

But we need systemd-resolved to be back before the connectivity check (or have some other workaround in place).