Please read the complete history of the bug, that you referenced: https://bugs.debian.org/1054541.
Then you will notice, that this is not a bug but a feature of apparmor. If you want to start privoxy with a config file, which is not located in /etc/privoxy (like /path/to/configuration/file), this is blocked by apparmor. You have several options to work around this problem: - disable apparmor (completely or only for privoxy) - place the config file in /etc/privoxy - copy /usr/sbin/privoxy to some other path (than apparmor doesn't trigger) From my point of view this isn't a bug but intended behavior (otherwise apparmor does not make much sense). ** Bug watch added: Debian Bug tracker #1054541 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054541 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2107690 Title: Cannot read configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/2107690/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
