And still does not work in Eoan Ermine (19.10).
apparmor-utils 2.13.3-5ubuntu1 amd64
# aa-logprof
ERROR: Values added to a non-existing variable @{HOMEDIRS}:
/shared/home/ in tunables/home.d/site.local
In fact, this bug was the origin cause of multiple packages failing to upgrade
when switching to eoan.
It puzzles me, that this was not detected within release testing and is not
getting more attention by the developers.
--
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/1331856
Title:
apparmor-utils don't work when defining a variable on
<tunables/home.d>
Status in AppArmor:
Triaged
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
When a variable is set in tunables/home.d/ the apparmor-utils programs
don't work and return this error messages:
root@ws24:~# aa-logprof
Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in <module>
apparmor.loadincludes()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4643, in
loadincludes
load_include(fi)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4520, in
load_include
incdata = parse_profile_data(data, incfile, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2839, in
parse_profile_data
store_list_var(profile_data[profile]['lvar'], list_var, value,
var_operation)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3279, in
store_list_var
raise AppArmorException(_('Values added to a non-existing variable: %s')
% list_var)
apparmor.common.AppArmorException: 'Values added to a non-existing variable:
@{HOMEDIRS}'
root@ws24:~#
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1331856/+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
