I am not totally sure how to reproduce this issue. I see in the changes
there is a "revert". Was that what trigger the behavior?
If you have issues with multiple snaps, I wonder if there is an issue
with snapd.apparmor.service
Could you look through your journal for a the boot and see if
snapd.apparmor.service was completed before any .service coming from
snaps?
What is the status of snap.lxd.daemon.unix.socket ?
Could you provide the output of:
journalctl -b0 -u snapd.service -u snapd.apparmor.service -u 'snap.*'
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2161401
Title:
Can't run certain snaps due to namespace mounting issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2161401/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
