Public bug reported:
On a debian stretch host with a working apparmor installation, I created
a container (nspawn) and installed apparmor within that container.
Within the container, apparmor can't be started. `systemctl status
apparmor` returns "ConditionSecurity=apparmor was not met". I also no
Probably related to
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1652101
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765130
Title:
Can't use apparmor-utils in nspawn container
To mana
This has definitely not been fixed in Maverick. I got the problem with a
Seagate ST31000520AS and a Samsung HD103SJ.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/638765
Title:
udisks wakes up unmou
According to http://bugs.freedesktop.org/show_bug.cgi?id=26508#c0, the
following would be a permanent workaround:
Create a file /etc/udev/rules.d/80-udisks.rules with the following
contents:
KERNEL=="sd*[!0-9]", ATTR{removable}=="0", ENV{ID_BUS}=="usb",
ENV{DEVTYPE}=="disk", ENV{UDISKS_DISABLE_P