Ah, interesting, TIL that focal is a bit odd here: - we changed to usrmerge as default in the disco installer - we added the 'usrmerge' package to convert old installations to this format in hirsute: https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/1906671
So, if you installed with focal, you'd have the usrmerge filesystem setup. If you initially installed with cosmic or earlier and upgrade, you won't get the usrmerge filesystem setup. Your system is less strange than I thought; sadly, now I'm even more confused how you're seeing what you're seeing. These /sbin -> /usr/sbin symlinks are so awkward, it's easy to draw incorrect conclusions about what's going on, so be very careful before proceeding, but I expect you can delete the /usr/sbin/apparmor_parser if that is actually a symlink and hopefully never think of this again. Be careful, of course, if you delete the only apparmor_parser on the system it'll be a pretty unhappy next reboot. I'd double-check ls -l /sbin /usr/sbin /sbin/apparmor_parser /usr/sbin/apparmor_parser a few times before deciding what, if anything, to delete. Thanks -- 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/2017594 Title: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker Status in apparmor package in Ubuntu: Confirmed Bug description: There appears to be two copies of apparmor_parser installed by previous versions of the apparmor package, in /sbin and /usr/sbin. When updating the apparmor package to apparmor-2.13.3-7ubuntu5.2, only the /sbin/apparmor_parser executable is updated and the /usr/sbin copy is left unchanged. Being earlier the path, /usr/sbin/apparmor_parser is used by Docker when trying to register the docker-default apparmor profile for containers. The orphaned older executable reports a warning about a new parameter in the parser configuration file in the same package, and that warning breaks the version check that docker runs against that executable on the first line of output. trying to parse the warning while looking for the version number results in the error: docker: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: strconv.Atoi: parsing "file": invalid syntax. As a workaround, we've been replacing the old version in /usr/sbin with a symlink to the file in /sbin, but the package should be corrected to do appropriate behaviour (either delete the unnecessary(?) copy in /usr/sbin or replace it with a symlink) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2017594/+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
