> Which are the perceivable consequences of this bug?
I currently cannot survey the consequences, since I am not familiar with
the recent semantic changes of apparmor (are there any docs? Any hints
to the users about changes? Any release notes?)
For some time now I am spending and wasting lots of time to hunt bugs in
all sorts of software like firefox, chromium, ejabberd, lxd,... which is
all caused by sudden apparmor trouble.
A side effect of all these bugs is that log files (and desktops through
aa-notify) are flooded with hundres, thousands, millions of log messages, which
jams a system and makes it impossible to find really important log messages,
and, btw., can ruin flash memory in SSDs and SD-Cards within short time.
Why on earth has one backported this pile of bugs into a LTS version?
This rendered Ubuntu so unreliable, that I have to consider to change to
CentOS or something like this for servers in order to get SELinux
instead.
Is there any way to get 16.04 stable again?
BTW: How should I answer the question about the consequences of the bug,
if I don't see any docs about was has changed with apparmor?
** Changed in: isc-dhcp (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654624
Title:
dhcp apparmor profile complains about lxd client
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
