Just a ping in case anyone thought that would resolve itself - it does not :-/
I've just hit it on x86 with the same symptoms as before - privileged container, never fully booting as snapd.seeded will never conclude being stuck in "activating".
As outlined in comment #4, I'm fine if the stance is "snaps in privileged containers are not meant to work".
But then PLEASE let them not stop/stall the rest of the system from working fine.
Have the snapd.seeded and/or others detect that siuation and stop trying instead of hanging indefinitely and thereby blocking everything else.
Just a ping in case anyone thought that would resolve itself - it does not :-/
I've just hit it on x86 with the same symptoms as before - privileged container, never fully booting as snapd.seeded will never conclude being stuck in "activating".
As outlined in comment #4, I'm fine if the stance is "snaps in privileged containers are not meant to work".
But then PLEASE let them not stop/stall the rest of the system from working fine.
Have the snapd.seeded and/or others detect that siuation and stop trying instead of hanging indefinitely and thereby blocking everything else.