I can no longer reproduce the original problem on current Zesty. I also tried downgrading to what I think would have been active at the time of my original report (tor and kernel versions known; I hadn't noted the apparmor version though). This is as below, but I still cannot reproduce.
root@test:~# dpkg-query -W tor
tor 0.2.9.9-1ubuntu1
root@test:~# dpkg-query -W apparmor
apparmor 2.11.0-2ubuntu1
root@test:~# uname -a
Linux test 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
It definitely was reproducible in my original report. I have not been able to pin down what changed, so marking Incomplete for now, as it could be me or my environment. But for now, tor appears to be working correctly by default on Zesty, which was my goal in tackling this.
I can no longer reproduce the original problem on current Zesty. I also tried downgrading to what I think would have been active at the time of my original report (tor and kernel versions known; I hadn't noted the apparmor version though). This is as below, but I still cannot reproduce.
root@test:~# dpkg-query -W tor
tor 0.2.9.9-1ubuntu1
root@test:~# dpkg-query -W apparmor
apparmor 2.11.0-2ubuntu1
root@test:~# uname -a
Linux test 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
It definitely was reproducible in my original report. I have not been able to pin down what changed, so marking Incomplete for now, as it could be me or my environment. But for now, tor appears to be working correctly by default on Zesty, which was my goal in tackling this.