Apparmor clutter in dmesg?

[NetwarSystem]

I have a handful of applications I use on Ubuntu 20.04 that come as snap packages, mostly comms stuff - Discord, Telegram, Wire. All of these applications spew junk into dmesg on a nonstop basis due to apparmor and there isn't any obvious way to make it stop.

Nothing in /etc/appamor or /etc/apparmor.d seems to stop this.

I spent some time with aa-teardown and aa-disable, no joy there. Disabling apparmor with systemd didn't seem to help. I care not at all about what the programs listed in /var/lib/snapd/apparmor/profiles do, so I wiped that directory, which mostly cleaned up dmesg, at the expense of none of the three apps I mentioned being able to run.

I'm really puzzled as to the thought process that lead to this configuration being created in the first place. I've been using Unix since about the time dmesg was added and it's always been the command line view into the kernel ring buffer, a place where one could see particulars regarding system hardware. Absolutely nothing in userland should be getting under foot in there. Continuous notification of activity makes sense for someone who is tuning applications that are using apparmor, but alias of aa-log to tail -f of something in /var/log seems like the right way to go about doing that.

So ... how does one ban snap apps from doing this?

[NetwarSystem]

There's a simple solution to this - install auditd and apparmor will stop using the kernel buffer. The apparmor guys had a solution within about half an hour.