Comment 20 for bug 1709155

It's always bee the case that a properly configured kernel is needed for snapd to work. There even have been features added, and bugs fixed, in the kernel as a direct result of needing features working for snapd (and in those cases the Ubuntu kernel has often shipped the patches before they were upstream, and in fact there might be still patches that need upstreaming; for example I'm not sure if the fix for https://bugzilla.kernel.org/show_bug.cgi?id=195453 has been picked up or not).

Just saying 'newest' carries no information as to whether the needed features are available and enabled on the kernel you're running.

What snapd should do, what we're trying to have it do, is determine what features are available and use them, and work around those that are missing.

This might result in some snaps not working properly or, in extreme cases, snaps running with only partial confinement (in these cases snapd should be warning about it). _This_ bug is about our failure to do this properly, at least in some scenarios.

If your bug is about something else, yes you should file a new bug. However, if you run a random kernel with an arbitrary feature set, I'm not sure what support you expect beyond snapd printing a warning about things not working properly (which is this bug).