privoxy crashes, fixed in upstream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
privoxy (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: privoxy
Using Feisty 7.04, and the privoxy installed from universe, i.e. Privoxy 3.06-1, I found that privoxy kept crashing at some point, probably when nobody was using it (single user desktop and only noticed failure when I returned to PC). Restarting privoxy was workaround but crash kept happening. There were no messages about a crash in the privoxy /var/log/
I downloaded source for latest stable version from http://
This may also be fixed in hardy's 3.07, but since this bug makes Privoxy quite unreliable, and useless for a network installation, a backport would be nice.
For those who aren't ready to upgrade, or if hardy doesn't fix this, try installing it under /usr/local - checkinstall makes it quite easy to do this. Here's my HOWTO on how to do this: http://
Details of original Feisty package used:
Package: privoxy
Priority: optional
Section: universe/web
Installed-Size: 2804
Maintainer: Ubuntu MOTU Developers <email address hidden>
Original-
Architecture: i386
Version: 3.0.6-1
Depends: libc6 (>= 2.5-0ubuntu1), libpcre3 (>= 4.5), logrotate, adduser
Recommends: doc-base
Filename: pool/universe/
Size: 1278504
MD5sum: ae60095d7ecd7a3
SHA1: a6cfee10554f3ec
SHA256: d5f5ed62f0ffdf6
Description: Privacy enhancing HTTP Proxy
Privoxy is a web proxy with advanced filtering capabilities for
protecting privacy, filtering web page content, managing cookies,
controlling access, and removing ads, banners, pop-ups and other
obnoxious Internet junk. Privoxy has a very flexible configuration
and can be customized to suit individual needs and tastes. Privoxy
has application for both stand-alone systems and multi-user networks.
.
Privoxy is based on Internet Junkbuster (tm).
.
Homepage: http://
Bugs: mailto:<email address hidden>
Origin: Ubuntu
3.0.9 is now the latest version, so I'm assuming that this has been fixed, and as such I am marking it as Fixed Released. If the issue still exists, please reopen the report.