Please could someone affected confirm that, without any workaround,
reverting to the previously published package resolves the issue, and
that upgrading back causes it to arise again? Then we can gain some
confidence that reverting the update is an appropriate course of action.

It looks like the previously published package version was
4.0.0-beta3-0ubuntu3 and this is the version in the release pocket. In a
default installation I believe that only apparmor and libapparmor1 are
installed on vanilla Ubuntu. If this the case, you should be able to
revert with:

sudo apt install apparmor=4.0.0-beta3-0ubuntu3
libapparmor1=4.0.0-beta3-0ubuntu3

You will be warned about a downgrade, but should receive no other
warnings (if you do receive any other warnings I suggest you do not
proceed).

To find the definitive list of packages that need downgrading you can
run this but you'd need to install the dctrl-tools package first:

grep-status -S apparmor|grep-dctrl -F Status installed -ns Package

Or you can consult /var/log/apt/history.log to understand what exactly
was upgraded.

See also bug 2064672 (thanks @g2p!) for details of the testing performed
on the package prior to release. It would be helpful if you could
participate in that bug to help us improve testing for next time - both
in improving our coverage of the QA steps performed, and in validating
the eventual fix if we do revert, to help us avoid regressing the
package again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072811

Title:
  Apparmor: New update broke flatpak with `apparmor="DENIED"`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to