@eurbah hi, also for the service in question, can you attach the output of `systemctl list-dependencies --after snap.<svc>.service`
AFAICT, all services are to be started after snapd.apparmor.d, which in turn is started after apparmor.service, which should ensure that apparmor profiles are loaded before service startup is attempted.
@eurbah hi, also for the service in question, can you attach the output of `systemctl list-dependencies --after snap.<svc>.service`
AFAICT, all services are to be started after snapd.apparmor.d, which in turn is started after apparmor.service, which should ensure that apparmor profiles are loaded before service startup is attempted.