So yes those look to be the culprit.
To snap-update.ns.slack profile you will need to add the rule
r @{run}/user/@{uid}/doc/,
you can do this to the generated profile (it will get thrown away when it gets regenerated but should be sufficient to test). The profiles are stored in
/var/lib/snapd/apparmor/profiles/
and then you can reload it with
sudo apparmor_parser -r /path/to/profile/file
and rerun the test
So yes those look to be the culprit.
To snap-update. ns.slack profile you will need to add the rule
r @{run}/ user/@{ uid}/doc/ ,
you can do this to the generated profile (it will get thrown away when it gets regenerated but should be sufficient to test). The profiles are stored in
/var/ lib/snapd/ apparmor/ profiles/
and then you can reload it with
sudo apparmor_parser -r /path/to/ profile/ file
and rerun the test