In my case it was caused by a bad AppArmor profile being present and loaded in complain (or enforce?) mode in
/etc/apparmor.d/usr.bin.snap
This apparently lead to snap not being able to determine the number of the snap and therefor caused a bad profile to be added to AppArmor.
"aa-status" outputed lines such as:
/usr/bin/snap//null-/usr/lib/snapd/snap-confine
for being in enforce mode
I moved that file (/etc/apparmor.d/usr.bin.snap
) to my home directory, ran "sudo aa-remove-unknown" and "sudo systemctl restart apparmor" after which everything was back to normal.
However I don't know the origins of /etc/apparmor.d/usr.bin.snap
so keep in mind that there might be something wrong with the system.