With snapd 2.55.3+22.04ubuntu1 and apparmor 3.0.4-2ubuntu2 from Ubuntu 22.04 (Jammy Jellyfish) :
- On a machine with a powerful i7-7700 HQ processor, the issue did NOT appear yet.
- On a machine with the slower AMD FX-8370E processor, the issue occurs systematically after each reboot.
$ sudo systemd-analyze critical-chain apparmor.service snapd.service
apparmor.service +396ms └─local-fs.target @3.660s
snapd.service +529ms └─basic.target @4.509s └─sockets.target @4.509s └─snapd.socket @4.505s +3ms └─sysinit.target @4.307s └─systemd-timesyncd.service @3.813s +494ms └─systemd-tmpfiles-setup.service @3.726s +77ms └─local-fs.target @3.660s
Workaround : After each reboot : $ sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/*
With snapd 2.55.3+22.04ubuntu1 and apparmor 3.0.4-2ubuntu2 from Ubuntu 22.04 (Jammy Jellyfish) :
- On a machine with a powerful i7-7700 HQ processor, the issue did NOT appear yet.
- On a machine with the slower AMD FX-8370E processor, the issue occurs systematically after each reboot.
$ sudo systemd-analyze critical-chain apparmor.service snapd.service
apparmor.service +396ms fs.target @3.660s
└─local-
snapd.service +529ms sockets. target @4.509s
└─snapd. socket @4.505s +3ms
└─sysinit. target @4.307s
└─systemd- timesyncd. service @3.813s +494ms
└ ─systemd- tmpfiles- setup.service @3.726s +77ms
└─local- fs.target @3.660s
└─basic.target @4.509s
└─
Workaround : After each reboot : snapd/apparmor/ profiles/ *
$ sudo apparmor_parser -r /var/lib/