Still a problem here (up to date with kernel 2.6.31-14) on one of two installations. I wonder if it's anything to do with peculiarities of the hardware, and in particular the problem occurs on a pretty fast box (boots in under half a minute). Workaround was to rename /etc/rc2.d/S20privoxy to /etc/rc2.d/S30privoxy - not happy with this, but it fixes the problem. Possibly the privoxy start script fails to check (and wait?) for something else to be loaded before trying to initialize?
-- privoxy not start at boot - karmic https://bugs.launchpad.net/bugs/427625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
