Bug 558748

Description of problem:

I've been using privoxy-3.0.13-beta.1.fc12.1.x86_64.rpm since upgrading F11->F12.  That version seems hosed.  I frequently get connection errors; perhaps 1 in 20 of new tabs/windows/URLs opened fail.  When they fail, either I get a privoxy error message, or I get a 404-like error message from the site itself.  Just to add to the surprise/confusion/screwiness factor, occasionally when I'm opening tabs from multiple sites, say sites X and Y, opening a new tab with some URL at site X will take me to a page on site Y.  It's really messed up.

I grabbed 3.0.15-beta from the sourceforge page and built from source.  I've been running 3.0.15-beta successfully without any problems.  I think 3.0.13-beta is hosed and pretty much unusable; in contrast, 3.0.15-beta is much better and I haven't encountered any more of those errors.

Can I suggest generating a new privoxy package with 3.0.15-beta and pushing that to updates, or at least updates-testing?

(To get 3.0.15-beta, I started from the 3.0.13-beta.1 src rpm, extracted the sources, replaced the 3.0.13-beta source tarball with the 3.0.15-beta source tarball, and tweaked the spec file.  I deleted the two patches, because 3.0.15-beta doesn't seem to have a inittab file of the proper form anymore.  That was a quick hack.  Similarly, as a quick hack I deleted all references to the logrotate file.  When packaging 3.0.15-beta, to do it right, you'll probably have to add some patches to install a reasonable /etc/init.d/privoxy script and a reasonable /etc/logrotate.d/privoxy script.  So, packaging up 3.0.15-beta isn't going to be a totally trivial task for the package maintainer.  But hopefully it shouldn't be too bad, and since 3.0.13-beta seems so broken, it's probably necessary.)


Version-Release number of selected component (if applicable):

privoxy-3.0.13-beta.1.fc12.1.x86_64.rpm

How reproducible: Reproducible if you browse for a while.  For me, one fairly reliable way to reproduce was to visit nytimes.com (potentially with another site open in another tab), and middle-click on a bunch of links to open them up in a new tab.  It took a little while, but eventually I started seeing hosage.  The only way I could find to recover from the hosage was to restart privoxy (service privoxy restart).