FYI this also breaks "systemctl restart snapd.seeded.service" in the same environment, and since this is unconditionally called from /var/lib/dpkg/info/snapd.postinst any snapd update on such a system will get stuck forever.
The former workaround of stopping the snapd.seeded unit thereby is not a valid mitigation anymore as soon as there is a snapd update. This also affects snapd.failure.service which is stuck on restart in this environment as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952084 Title: snapd.seeded.service never finishes when privileged or nested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1952084/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
