Is anyone able to suggest snaps that cause this error on launch? I tried mattermost-desktop and mailspring which people had issues with and I had no issue loading them

cannot change profile for the next exec call: No such file or directory
snap-update-ns failed with code 1: No such file or directory

It doesn't seem like issue with specific snaps but rather snap daemon. Any snap that you install without --classic argument can cause the issue.
Yesterday I had to run sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/* every time after installing snaps but today everything (installing, running, etc) works fine.

In T6499#124708, @mati865 wrote:

It doesn't seem like issue with specific snaps but rather snap daemon. Any snap that you install without --classic argument can cause the issue.

Just needed one example :P

but today everything (installing, running, etc) works fine.

So it's not an issue anymore then?

In T6499#124711, @sunnyflunk wrote:

In T6499#124708, @mati865 wrote:

It doesn't seem like issue with specific snaps but rather snap daemon. Any snap that you install without --classic argument can cause the issue.

Just needed one example :P

Snaps you mentioned should expose problems if something goes wrong. Yesterday helm and postman snaps weren't working for me unless I reloaded AppArmor rules.

but today everything (installing, running, etc) works fine.

So it's not an issue anymore then?

Today it works for me but if you look into other reports this issue persists across multiple boots.

If you have further issues, run

sudo usysconf run -f

I'm pushing a package which should resolve it for any remaining stragglers.

Still an issue with Spotify, with a clean install (2 weeks old). Each time I reboot my computer, I have to

sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/*

@Paradoxeuh I updated snapd D4893, so this should solve it

I'm wondering if it's not aa-lsm-hook issue because snapd works fine with Apparmor on Arch Linux.

@Paradoxeuh when you run into the issue next time please run systemctl status snapd.apparmor.service and post it's output.

@Girtablulu So far so good, it seems fixed. Thanks !

I'm expriencing this problem on a basically newly-installed Solus 4 on most reboots. Running sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/* fixes it. Here's the snapd.apparmor.service status:

● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/usr/lib/systemd/system/snapd.apparmor.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

Same error on fresh Solus 4 install. After installing the KeepassXC snap it works, after a reboot not anymore.

Running

sudo usysconf run -f

apparently fixed it (after two reboots it still works).

After installing the KeepassXC snap it works

Why would you install keepassxc snap? We have it in the repo (it's named keepassx but uses the correct fork).

You removing my comment (which was an answer to your question why I did install the snap and my UX with Solus) without a word to me, not even answering my question (why it is confusingly named)?
I am currently really disappointed with your project culture here.
If you deem my comment off-topic than so is your last one.

(I did not find a way to contact you after examining your profile either. However, an answer here at least, explaining why you removed my comment, would be common courtesy.)