Load the transmission-daemon apparmor profile in the upstart init configuration file.

[David]

I am using the apparmor transmission-daemon profile attached to this bug report and on boot it is not 'applied' because the transmission-daemon can start up before its apparmor profile is loaded. This issue can normally be fixed by adding a /lib/init/apparmor-profile-load $profile_name to the upstart configuration pre-start script.

[David (d--)]

Actually I am not sure that this bug is best fixed this way. Unfortunately the pre-start script is not able to load the apparmor profile because the upstart setuid and setgid directives have already been applied. So instead this bug can be fixed by including a symbolic link to the transmission-daemon apparmor profile in /etc/apparmor/init/network-interface-security/ .