Comment 44 for bug 131976

Is it possible this problem is caused by a sequencing problem with the Live CD scripts? I run the Karmic LiveCD in persistent mode on a hard disk drive. Once I am logged in to Ubuntu, I can run 'sudo /etc/init.d/apparmor start' and see no errors in the terminal nor the log files. The kernel log shows all the aparmor profiles are loaded. Everything works normally.

In looking at the Karmic initrd.lz content, it appears that the '/init' script calls '/scripts/init-bottom/apparmor', which then tests for the existence of a file called '/scripts/casper-bottom/42disable-apparmor'. The latter file will be found when booting with the Live CD software, and finding that file will cause '/scripts/init-bottom/apparmor' to early exit instead of loading the apparmor profiles. The apparent reason for the early exit, in lieu of loading the profiles, is the assumed failure of apparmor to deal deal with the union file system created by the live CD software. BUT, when the early exit is taken, the '/scripts/casper' script that sets up the union files system has NOT YET RUN, as far as I can see, so of course apparmor would have a problem finding and loading profiles?

Is it possible that simply changing the apparmor profile load process to follow the creation of the union file system, would allow apparmor to execute properly? It seems like an odd coincidence that lots of software EXCEPT apparmor appears to run flawlessly on the 'stacked' file system, and that apparmor is happy to load profiles after booting the Live CD?