First sorry for my english.. not really good at it.
So, this is a old bug that was fixed in some patches ago, but it's still happening with me on Solus KDE.
After installing a snap and reboot, that snap stops working, when I run the snap via terminal a got this:
"snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks"
so i ran sudo apparmor_status
and got this:
sudo apparmor_status
apparmor module is loaded.
8 profiles are loaded.
8 profiles are in enforce mode.
/snap/core/8592/usr/lib/snapd/snap-confine
/snap/core/8592/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
snap-update-ns.core
snap-update-ns.snap-store
snap-update-ns.whatsdesk
snap.core.hook.configure
snap.snap-store.snap-store
snap.whatsdesk.whatsdesk
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
then if i run sudo usysconf run apparmor -f
and sudo apparmor_status
i got this:
sudo apparmor_status
apparmor module is loaded.
17 profiles are loaded.
17 profiles are in enforce mode.
/snap/core/8592/usr/lib/snapd/snap-confine
/snap/core/8592/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
/usr/lib64/snapd/snap-confine
/usr/lib64/snapd/snap-confine//mount-namespace-capture-helper
klogd
lsb_release
nvidia_modprobe
nvidia_modprobe//kmod
ping
snap-update-ns.core
snap-update-ns.snap-store
snap-update-ns.whatsdesk
snap.core.hook.configure
snap.snap-store.snap-store
snap.whatsdesk.whatsdesk
syslog-ng
syslogd
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
doing this fix the problem but after i restart again the problem is back.