Comment # 6 on bug 1090477 from Atri Bhattacharya

Sorry George, I haven't been able to pay this enough attention until now. I
just tried to run this on an openSUSE 42.3 VM and I am unable to reproduce the
problem (or may be not quite doing the same thing). When you use torbrowser
from upstream, do you also install and use the apparmor profile (modified for
the upstream binary wherever you save it)? If you do that, that would be a like
for like comparison between the upstream bundle and our package, and we will
know whether this problem is a) apparmor related and b) upstream or some
downstream issue. One other thing: do you still see the bug with apparmor
disabled? E.g. do
sudo systemctl stop apparmor.service 
then try running torbrowser again.