sorry, I jumped the gun slightly and mis read a mount line and a piece of code. The nosuid option does interact with this but is not whats causing the clearing of the personality. Execution of any setuid binary will cause the personality to get cleared, so using either su or sudo to switch from user to root clears the personality.
The net effect is no different however in that on boot READ_IMPLIES_EXEC is set, so apparmor is being asked for the extra 'm' permission. The best solution at the moment if you want a single policy set for all x86 machines is to just include the 'm' permission. -- apparmor broken after reboot on i386 https://bugs.launchpad.net/bugs/202161 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
