Package: xul-ext-torbirdy Version: 0.1.3-1 Severity: grave Justification: renders package unusable
Dear Maintainer, I recently installed Torbirdy using the pkg xul-ext-torbirdy in order to have connection to system tor by default. When I open icedove, I do not see the typical green text at the bottom of the status bar stating "Torbirdy Enabled: Tor"... so I purged the pkg and reinstalled, with no change. I then purged the pkg again and installed from Icedove add-ons, and it worked as intended, albeit it uses the "wrong" port (9150) for Tor instead of system tor's 9050 as discussed in previous bug reports. I much prefer to use the system Tor since tor for jessie/stable has been built with seccomp sandboxing capability while I'm not sure if Tor for TBB has. Let me know if I can help with anything to facilitate the package being updated. Many thanks, Ben -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xul-ext-torbirdy depends on: ii icedove 31.7.0-1~deb8u1 ii tor 0.2.5.12-1 xul-ext-torbirdy recommends no packages. xul-ext-torbirdy suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
