[23:25] <zyga> I reproduced the case where snapd hangs on focal update
[23:25] <zyga> root       19671  0.0  0.0   2600  1692 pts/1    S+   15:21   0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8
[23:25] <zyga> root       19751  0.0  0.1  20592  3608 pts/1    S+   15:21   0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service
[23:25] <zyga> snapd is not seeded correctly
[23:25] <zyga> has no changes
[23:25] <zyga> but I'm also surprised by starting of _all_ of those units here
[23:26] <zyga> Setting up snapd (2.44~pre1+20.04) ...
[23:26] <zyga> Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ...
[23:26] <zyga> Created symlink /etc/systemd/system/multi-user.target.wants/snapd.recovery-chooser-trigger.service → /lib/systemd/system/snapd.recovery-chooser-trigger.service.
[23:26] <zyga> snapd.failure.service is a disabled or a static unit, not starting it.
[23:26] <zyga> snapd.snap-repair.service is a disabled or a static unit, not starting it.
[23:26] <zyga> seeding never completes, though https://www.irccloud.com/pastebin/CUEBrm6F/
[23:31] <zyga> state.json from this wonky state https://www.irccloud.com/pastebin/wYgT3mTZ/