http://bugzilla.opensuse.org/show_bug.cgi?id=1090477 http://bugzilla.opensuse.org/show_bug.cgi?id=1090477#c6 --- Comment #6 from Atri Bhattacharya <badshah400@gmail.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.