This bug was fixed in the package firejail - 0.9.62.4-3 --------------- firejail (0.9.62.4-3) unstable; urgency=medium
* Import compatibility fix for AppArmor 3.0. (LP: #1899334) * Symlink test sources to d/missing-sources so lintian can find them. -- Reiner Herrmann <rei...@reiner-h.de> Sat, 17 Oct 2020 13:41:00 +0200 ** Changed in: firejail (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1899334 Title: firejail AppArmor profile not compatible with AA 3.0 Status in apparmor package in Ubuntu: New Status in firejail package in Ubuntu: Fix Released Bug description: firejail installation logs: > Found reference to variable run, but is never declared On system startup or "systemctl restart apparmor", this leads to a service fail: > root@sys:~# systemctl restart apparmor > Job for apparmor.service failed because the control process exited with error code. > See "systemctl status apparmor.service" and "journalctl -xe" for details. It helps to add "include <tunables/run>" to /etc/apparmor.d/firejail- default Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp