(In reply to Aleksey Kontsevich from comment #38)
> > sudo systemctl restart apparmor.service
>
> did not helped for some reason, so forced to restart PC.
Wild guess: The snap profiles live in /var/lib/snapd/apparmor/profiles/, right?
"systemctl restart apparmor" will only reload the profiles in /etc/apparmor.d/, so you'll need to somehow force snap to reload the profile. Of course, rebooting is a way to do this, but maybe
apparmor_parser -r /var/lib/snapd/apparmor/profiles/
is less annoying ;-)
(I don't use snap, therefore i don't know if there is a more "official" method to force a reload of its AppArmor profiles.)
(In reply to Aleksey Kontsevich from comment #38)
> > sudo systemctl restart apparmor.service
>
> did not helped for some reason, so forced to restart PC.
Wild guess: The snap profiles live in /var/lib/ snapd/apparmor/ profiles/ , right?
"systemctl restart apparmor" will only reload the profiles in /etc/apparmor.d/, so you'll need to somehow force snap to reload the profile. Of course, rebooting is a way to do this, but maybe snapd/apparmor/ profiles/
apparmor_parser -r /var/lib/
is less annoying ;-)
(I don't use snap, therefore i don't know if there is a more "official" method to force a reload of its AppArmor profiles.)