[I'm not talking for the Tor folks here; this is my own opinion.]
I think the primary concern of upstream is that users get current Tor
versions when they ask for Tor. Historically that has been a problem in
Ubuntu, where users apt-get installed (or whatever the shiney equivalent
for that is
fine workaround.
>
>
> I wonder what we have to do to fix this within Ubuntu itself?
I wonder if we're running into #822349 - https://bugs.debian.org/822349
Are there any apparmor policies loaded other than Tor?
--
| .''`. ** Debian **
Peter Pa
** Bug watch added: Debian Bug tracker #822349
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822349
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568435
Title:
Tor cannot start `obfs4proxy`
> + On top of that, 2 changes were cherry picked from 0.3.0.10-1 and
0.3.0.4-rc-1 to use DAC_READ_SEARCH
If you're cherry picking, you might also want to consider the changes committed
to git that switch
the apparmor profile to use Pix instead of PUx, and maybe the sysV init script
fix.
cf.
Your screenshots don't look like anything the tor package ships.
It looks like torbrowser-launcher, which is at best related but is not
the Tor package.
** Package changed: tor (Ubuntu) => torbrowser-launcher (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
