Hi, one problem debugging this is that this problem occurs only if+when there is a new upstream version of torbrowser to be updated too, which only happens every 6-8 weeks or so.
It just occured to me that this problem can probably be tested anytime
though, by
- (enabling apparmor)
- launching torbrowser-launcher, which will install the latest stable
torbrowser
- configuring torbrowser-launcher to use alpha-releases.
- launching torbrowser-launcher to upgrade to said alpha release.
Currently as per this bug, this should fail. Once the profiles has been
fixed, this should work.
The above procedure should be usable for testing this anytime.
--
cheers,
Holger
signature.asc
Description: Digital signature
