Package: tor Version: 0.2.7.6-1 Severity: normal On a fresh unstable installation tor refuses to do anything. The situation seems to be different from #802521, hence a new bug report. If it turns out to be the same bug, feel free to merge.
Dez 18 13:16:08 feivel tor[1349]: Dec 18 13:16:08.001 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Dez 18 13:16:08 feivel systemd[1356]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Unit entered failed state. Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Failed with result 'exit-code'. Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Manually downgrading to 0.2.5.12-1 solved the problem for now. Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-rc4-next-20151211-1.g34634ae-vanilla (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tor depends on: ii adduser 3.113+nmu3 ii libc6 2.21-4 ii libevent-2.0-5 2.0.21-stable-2+b1 ii libseccomp2 2.2.3-2 ii libssl1.0.0 1.0.2d-1 ii lsb-base 9.20150917 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages tor recommends: ii logrotate 3.8.7-2 ii tor-geoipdb 0.2.5.12-1 ii torsocks 2.1.0-1 Versions of packages tor suggests: pn apparmor-utils <none> pn mixmaster <none> pn obfsproxy <none> pn polipo | privoxy <none> pn socat <none> pn tor-arm <none> pn xul-ext-torbutton <none> -- no debconf information
