[Pkg-privacy-maintainers] Bug#908463: Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

[Antoine Beaupré]

On 2018-09-10 16:58:06, gregor herrmann wrote:
> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>
>> Disabling the apparmor profiles fix this:
>> 
>> aa-complain torbrowser.Tor.tor
>> aa-complain torbrowser.Browser.firefox
>
> After upgrading to 0.2.9-4, adequate complains:
>
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox
>
> After getting rid of them, I have a starting torbrowser again.

After getting rid of them, apparmor collapses in a pile of error and
fails to start:

sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.firefox in /etc/apparmor.d/torbrowser.Browser.firefox at line 123: Could not open 'local/torbrowser.Browser.firefox' 
sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.plugin-container in /etc/apparmor.d/torbrowser.Browser.plugin-container at line 94: Could not open 'local/torbrowser.Browser.plugin-container' 
sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Tor.tor in /etc/apparmor.d/torbrowser.Tor.tor at line 41: Could not open 'local/torbrowser.Tor.tor' 

I doubt this is a real solution: those files are just empty here and
should not significantly change the AA policy.

A.

-- 
>From the age of uniformity, from the age of solitude, from the age of
Big Brother, from the age of doublethink - greetings!
                        - Winston Smith, 1984