Thanks Etienne, this is a bit surprising! Do I understand correctly,
that on the slower machine (where you are seeing this bug) you will not
be able to start firefox until you have run that apparmor_parser
command? Not even if you try starting firefox well after the login?
It's strange, because your logs show that the apparmor.service unit was
started can you please also attach the output of these commands:
sudo systemctl status apparmor
sudo journalctl -b _SYSTEMD_UNIT=apparmor.service + SYSLOG_IDENTIFIER=audit
And then also this (make sure you haven't previously started firefox in
this boot):
SNAPD_DEBUG=1 firefox
And after that, let's have a look at the full system log (I have no
clear idea what to look for, actually, but maybe I'll spot something
suspicious):
sudo journalctl -b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871148
Title:
services start before apparmor profiles are loaded
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
