As mentioned, this was is on an Ubuntu Touch system and it happens on boot. It is still the case as of today. I don't know much about the container flip on Touch devices, but right now, the apparmor profile is not in effect on these systems. I can confirm this on the Nexus 7 (grouper) and Nexus 4 (mako).
Unfortunately, today someone (vila) reported the following denial during a test run:
/var/log/syslog: Oct 8 09:16:26 saucy-i386-20131008-0916 dbus[499]: apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=634 profile="lxc-container-default" peer_profile="lxc-container-default" info="Permission denied"
I think this indicates a race condition where lxc somehow won the race and the profile was in effect, but the profile itself is missing needed rules because no one has actually seen/noticed this condition due to this bug.
As mentioned, this was is on an Ubuntu Touch system and it happens on boot. It is still the case as of today. I don't know much about the container flip on Touch devices, but right now, the apparmor profile is not in effect on these systems. I can confirm this on the Nexus 7 (grouper) and Nexus 4 (mako).
Unfortunately, today someone (vila) reported the following denial during a test run: 20131008- 0916 dbus[499]: apparmor="DENIED" operation= "dbus_method_ call" bus="system" path="/ org/freedesktop /DBus" interface= "org.freedeskto p.DBus" member="Hello" mask="send" name="org. freedesktop. DBus" pid=634 profile= "lxc-container- default" peer_profile= "lxc-container- default" info="Permission denied"
/var/log/syslog: Oct 8 09:16:26 saucy-i386-
I think this indicates a race condition where lxc somehow won the race and the profile was in effect, but the profile itself is missing needed rules because no one has actually seen/noticed this condition due to this bug.