some snap related errors are printed to the terminal at boot time, and then subiquity doesn't start. Jumping to tty2 and doing a simple
systemctl status snapd
shows that snapd complains about the state of the core18 snap, and indeed /snap/core18/current/ is empty. Reinstalling core18 and refreshing subiquity from the candidate channel makes it start normally. This looks like a problem in the snap seeding.
In the recent focal-live- server- amd64 dailies, e.g. in:
Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20211124)
some snap related errors are printed to the terminal at boot time, and then subiquity doesn't start. Jumping to tty2 and doing a simple
systemctl status snapd
shows that snapd complains about the state of the core18 snap, and indeed /snap/core18/ current/ is empty. Reinstalling core18 and refreshing subiquity from the candidate channel makes it start normally. This looks like a problem in the snap seeding.