Hi, u: > I can't reproduce this on a stable system using the latest > torbrowser-launcher from jessie-backports.
> Did you test this on a clean installation? A clean installation won't expose this bug: it can only happen when one had installed a version that shipped /etc/apparmor.d/torbrowser.start-tor-browser and later upgraded to one that doesn't anymore. I *thought* I had fixed this bug already: torbrowser-launcher (0.2.5-1) unstable; urgency=medium […] * Remove obsolete conffile /etc/apparmor.d/torbrowser.start-tor-browser thanks to Paul Wise. (Closes: #805706) … but apparently I failed to get the rm_conffile line right. Cheers! -- intrigeri