** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785391
Title:
aa-genprof fails in an lxd instance
To manage notifications about
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785391
Title:
** Changed in: apparmor
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785391
Title:
aa-genprof fails in an lxd instance
To manage notifications about this
Fix commited to 2.10 branch..master
For the aa-logprof issue you mentioned, please answer my question in a
new bugreport ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785391
Title:
aa-genprof
https://gitlab.com/apparmor/apparmor/merge_requests/157
For aa-logprof - a) what exactly is the problem and b) please answer in
a separate bugreport ;-)
** Changed in: apparmor
Status: New => Triaged
** Changed in: apparmor
Assignee: (unassigned) => Christian Boltz (cboltz)
--
You
Funny enough, aa-logprof doesn't work well in a guest on my system
either:
# aa-logprof
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
This could be because the host system is running auditd.
I have no idea what happens if the host isn't running auditd.
