Hi, this bug is gone, but users users might be affected from a fall-out from it: upgrades to alpha/beta versions have appearantly modified the the users config to prefer such releases, so that even with newer versions this bug seems still to be there, while indeed the bug is now in the user's configuration files.
As there is not really a way to find out if this change was done by bug or on
purpose, the user has to cleanup her configs manually.
To remove the config manually:
rm ~/.config/torbrowser/ -r
Thus leaving this bug closed now :)
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
