Comment 4 for bug 1860550

I think the reason you see snapd get stuck on boot is because with the updated snap the seed.yaml is no longer valid. Missing or out of order bases, or content interfaces, would typically do this.

'snap debug validate-seed' was added in 2.39, and expanded in 2.41 to report on these issues.

There is not much snapd can _do_ on a system with an invalid seed; it needs checking before creating the system image.

I'm setting snapd's bug task to Invalid, but if there is something snapd needs to do please let us know (set it back to New so our triage picks it up).

Thank you.