Comment 12 for bug 1946656

The issue can indeed be reproduced by jumping to a shell from the very first subiquity screen and trying to `systemctl restart snapd`.

Doing a `systemctl stop snap.subiquity.subiquity-service` appears to unblocks snapd: it restarts reliably. Interestingly restarting snap.subiquity.subiquity-service doesn't reproduce the issue: subiquity starts correctly and snapd doesn't get hung anymore.