On Mon, 10 Sep 2018 11:17:54 -0400, Antoine Beaupré wrote: > > 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:
I first aa-disable()d them before rm'ing them. > 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. Don't know, just sharing my experience and pointing to a packaging glitch. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Bob Dylan: I Shall Be Free
signature.asc
Description: Digital Signature
