Having discussed on IRC, I don't believe /etc/init/rc-sysinit.conf being delayed explains the symptoms described. User processes are started from a login session, which would be launched via lightdm; lightdm is 'start on runlevel and [...]', and the runlevel event is strictly later than the point at which we run the rcS scripts from rc-sysinit.conf.
If this were processes related to individual upstart jobs in /etc/init that might start before runlevel 2, then this could explain it; but given the problem described is with firefox being unconfined, that doesn't seem related to the delayed apparmor profile loading because firefox and lightdm are also delayed in that case.
Having discussed on IRC, I don't believe /etc/init/ rc-sysinit. conf being delayed explains the symptoms described. User processes are started from a login session, which would be launched via lightdm; lightdm is 'start on runlevel and [...]', and the runlevel event is strictly later than the point at which we run the rcS scripts from rc-sysinit.conf.
If this were processes related to individual upstart jobs in /etc/init that might start before runlevel 2, then this could explain it; but given the problem described is with firefox being unconfined, that doesn't seem related to the delayed apparmor profile loading because firefox and lightdm are also delayed in that case.