apparmor kernel 5.2

[paxmark1]

apparmor is now standard in Debian 10 - which is also Sparky 5  Therefore if it also standard in Sparky6 probably - Bullseye.  It was standard back in 2007 in Ubuntu, SUSE also uses, to best of my knowledge RH and it's variants still uses SELinux. 

Debian 10 contains 57,703 packages, supports UEFI Secure Boot,[42] has AppArmor enabled by default, uses LUKS2 as the default LUKS format, and uses Wayland for GNOME by default.[43

via
https://en.wikipedia.org/wiki/Debian_version_history#Debian_10_(Buster)

I lurk at Siduction forum, helpful hints and they get the problems 5 days before Sparky' s rolling might receive them.  This caught my eye  - it is translatable on their site.

https://forum.siduction.org/index.php?topic=7730.msg63091;topicseen#new

It is not an easy subject to understand, The apparmor home page is sparse and technical.  The Buster link points to Wikipedia.  Still quite technical.  The Debian wiki front page was written in 2017, old.  A subset is newer it lists the profiles as of January 2018 for Buster. 

Other info I found interesting was via the ChangeLog
https://metadata.ftp-master.debian.org/changelogs//main/a/apparmor/apparmor_2.11.0-3+deb9u2_changelog

The key word I see  in the changelog is Ubuntu - addtions and deletions of code.  Updated approx. annually. 

For me
"systemd-analyze blame" on a buster install has apparmor at #2 0.965 seconds, not too bad.  "journalctl -b -1 | grep apparmor is a swamp of entries. 

Cutting to the only recommendations I have is that if you have problems with kernel 5.2, especially with Firefox-esr  or libvirtd, possibly cups (might be affecting me  - s l o w)  apparmor might to blame

Towo has been the kernel guy ( he rolls them out) at Siduction for years.  Any suggestions he gives are primarily for the Siduction kernel, but they very well might apply to Sparky.  Then again, they might not. I am not an expert on kernels.  I am at 4.19 in Buster and Sid.     

I put this in "Other" as I have been investigating this on my non-Sparky main computer.  It is not as slow to start on my Sway WM  32 bit netbook and journalctl -b -1 | grep apparmor | less is more sparsely populated.  Of course my Sway system is sparse presently also.    On same netbook with over 3 year Sparky rolling lxqt apparmor does not slow down the start, but there are numerous instances listed in journalctl. 

So, possibly something to look for when problems arise.  And if you might be serious about finding a niche in the Debian ecosystem they would probably welcome you with open arms to investigate and write up profiles for apparmor.