** Changed in: privoxy (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/427625
Title:
privoxy not start at boot - karmic
To manage notifications about t
This was fixed with 3.0.16-1, see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=534735
** Changed in: privoxy (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: privoxy (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534735
Importance: Unknown
Status
On one of my 64-bit 10.4 machines, privoxy starts up and runs fine with
Firefox, but needs a restart before it will deign to accept connexions
from Opera 10.6. Both browsers are configured to use "localhost:8118" as
proxy.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/4276
Fiddler, can you verify that privoxy is even running?
Can you post the output of "sudo ps auxww|grep privoxy" and "sudo netstat -anp
| grep 8118"?
Oh, and to check if privoxy is not only running, but also you can connect to
try "telnet localhost 8118" or "telnet 127.0.0.1 8118".
By the way, over
The workaround from #44 (change localhost:8118 to 127.0.0.1:8118) didn't
work for me.
Running Lucid amd64, upgraded from Karmic. Privoxy was installed after
the upgrade (and wasn't installed before).
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this b
Running Lucid Lynx, found that firehol, dansguardian, privoxy stopped
working recently. Only error reported - in syslog - was dansgaurdian
unable to connect to proxy.
dansguardian[1741]: Error connecting to proxy
After updating Lucid this morning. Problem still apparent. privoxy
appears to be run
Update: problem gone after update to kernel 2.6.32-21 on the 10.4 beta
upgrade box mentioned in #42 - using standard privoxy startup scripts.
--
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, wh
This problem is strangely inconsistent for me across several machines
that I maintain. My laptop is currently running 10.4 beta, has been
running latest betas since Intrepid, and has never ever had a problem
with privoxy startup. Another machine which was OK with the 9.10 install
developed the prob
I'm having the same issue with 9.10, Privoxy 3.0.13-1 and the workaround
does NOT work in my case. I still get the same error messages
--
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
Bug affects me too, but the following workaround is successful (as mentioned
several times above):
1. disable ipv6 by adding "net.ipv6.conf.all.disable_ipv6 = 1" to
/etc/sysctl.conf
2. change all localhost lines to 127.0.0.1 in the /etc/privoxy/config file
3. reboot
--
privoxy not start at boot
same problem here
+ mostly very, very sluggish performance when running with opera 10.10 or
firefox 3.5.6
uninstall claimed to free 311MB disk space.
privoxy 3.0.13-1, karmic latest updates, kernel 2.6.31(-16?)
workaround ::1 autostarts here, but only works for firefox,
opera won't accept se
Is this ever going to be address by the package maintainers?
--
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.ubun
Roland,
Your uploaded 3.0.15-2 does not fix all the problems caused by this bug.
Your fix, if I'm not mistaken, forces privoxy to listen on IPv6 ::1
(localhost) instead of IPv4 127.0.0.1. This breaks IPv4 applications
that attempt to forward stuff to privoxy. the workaround that I use
until a fi
I just uploaded a new 3.0.15-2 version to the Debian archive, that should solve
this issue.
Maybe someone is interested to try out, whether this is the solution for you.
If the package is not available via the Debian archive, have a look at
http://www.spinnaker.de/debian/privoxy.html
--
privoxy
sorry, I gave the incorrect version of privoxy in my post above at #34.
Instead of 'Privoxy (version 2.0.0.23 (20090817))' it should read as
'Privoxy (version 3.0.13-1)'
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification because you ar
I had this problem running privoxy under Ubuntu karmic with all
available updates installed through 12 Dec 2009 :
Privoxy (version 2.0.0.23 (20090817)) installed but after a week or so,
it would never actually load, whether started from the command line or
by Vidalia.
All of privoxy's files were
Thanks Greg Eden for the workarounds on Tor.
I am using JAP Jondo instead, but I will try to use Tor this way.
Rgds.
Victor
--
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 subscribe
I'm wondering if this is related to
"rc2 currently does not wait for localhost"
from
https://wiki.ubuntu.com/FoundationsTeam/Specs/LucidUpstartServerReview -
which links to a possibly related bug in samba - bug #462169.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/42762
** Tags added: ubuntu-boot-experience
--
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.ub
FYI, I tried the above "listen address is set to 127.0.0.1:8118 instead
of localhost:8118" workaround and it didn't work for me. Privoxy still
failed to start on boot (although a later manual start worked fine).
>From /var/log/privoxy/logfile:
Error: Can not resolve 127.0.0.1: Address family for
** Description changed:
--
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/mailm
Since this also affects me with Ubuntu 9.10 (not with earlier versions),
I am setting this bug to "confirmed".
** Changed in: privoxy (Ubuntu)
Importance: Undecided => Low
** Changed in: privoxy (Ubuntu)
Status: New => Confirmed
--
privoxy not start at boot - karmic
https://bugs.launc
Confusion continues. With no apparent updates, and before I could apply
the IPv6 workaround, one of my machines has started working correctly
again, starting privoxy at startup.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification becaus
@ richardgv #27 - sorry, yes, I have the listen address as
127.0.0.1:8118 in my config too. Before this bug really took hold, that
was the first change necessary top get karmic working on comparison with
Jaunty. Glad those two workarounds work for you too.
--
privoxy not start at boot - karmic
Hopefully this bug can be fixed soon.
@Stevan Kew Ell
I just found the workaround works if listen address is set to "127.0.0.1:8118"
instead of "localhost:8118". Thanks.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification because you a
@Stevan Kew Ell
The workaround does not work for me. After disabling ipv6, I receive still the
same error:
Nov 17 11:02:53.989 b77028d0 Fatal error: can't bind to localhost:8118:
The hostname is not resolvable
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You rece
This has been driving me to distraction too, as the combination of
privoxy and epiphany-webkit is great. I think I have just stumbled onto
a temporary workaround, which hopefully will help to locate the bug. If
you disable IPv6, it starts correctly.
I put the line:-
net.ipv6.conf.all.disable_ip
I have the same issue. "127.0.0.1:8118" workaround doesn't work for me,
too. Reinstallation does not work, either.
Nov 14 10:38:19.591 b77198d0 Fatal error: can't bind to localhost:8118: The
hostname is not resolvable
Nov 14 11:36:50.056 b78ad8d0 Fatal error: can't bind to 127.0.0.1:8118: The
ho
hello,
After last kernel update for karmic, the bug is appear again.
I need all new start reinstall privoxy .
So bug still , depend of the kernel it seem.
best regards
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification because you a
On my desktop (wired ethernet only), changing the privoxy upstart script
to depend on $named seems to work, but it doesn't work on my notebook
(wireless only).
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification because you are a member
I'm running kubuntu so I don't get wireless until knetworkmanager has
run, -after- desktop login.
For me, Privoxy starts, but never seems to notice that I have a got a
network . It seems to assume that if there was no network when it
started up, there never will be one. So I have to restart the se
@836v
If you only want tor then you can bypass privoxy altogether. Just
Uninstall privoxy and set tor to use Socks5, 127.0.0.1 and port 9050. In
foxyproxy edit the setup to these settings and it will work without
privoxy.
cheers
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/b
ps
If the system will not let you uninstall privoxy without removing tor,
just leave it there and bypass with above settings. The changes you made
to the first line of privoxy config are ignored and can be removed.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You
I can confirm this problem ("hostname is not resolvable") with karmic rc
- the workaround with setting the listen-address to ::1 worked for me.
I work on a laptop with only WLAN connection - probably name resolution
is not available fast enough? I *think* I saw the same problem with
another daemon
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/r
Hello,
>From Karmic beta1 and all last updates, i have no more problem with
privoxy, it boot enable again.
So fixed for me
my best
--
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 s
Encountered the same on new install of 9.10, but not on the installation
I've been running since early alpha (both 64-bit). Changing the config
file to '127.0.0.1:8118' doesn't make any difference.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug
Per the above suggestion I reininstalled privoxy 3.0.13-1 but it still
does not start at boot.
Still seeing:
Sep 24 09:06:51.303 b805e8d0 Fatal error: can't bind to localhost:8118:
The hostname is not resolvable
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You re
well bug still, today i become this message:
Sep 23 11:25:34.732 7f11e92f26f0 Fatal error: can't check configuration
file '/home/starslights/config': No such file or directory
i have need reinstall again privoxy .
Kubuntu Karmic 9.10 64 bits, 2.6.31-10-generic and privoxy 3.0.13 on
home encryp
well , after restarted, privoxy are enable at start again.
So just reinstall privoxy and all will run again fine. The config will
not lost, it just fix the braked link.
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification because you are
hello,
i am on Kubuntu karmic 64 bits, 2.6.31-10-generic and privoxy 3.0.13 on
home encrypted
It have always right worked so far but from the last update , it was
unable to start at boot and don't find anymore the config.
I have reinstalled it and work again. I have not restarted the system
sinc
I can second this, for privoxy 3.0.13-01 on a fresh karmic alpha 6
install.
/var/log/privoxy/logfile reads
Fatal error: can't bind to localhost:8118: The hostname is not
resolvable
--
privoxy not start at boot - karmic
https://bugs.launchpad.net/bugs/427625
You received this bug notification be
Confirmed on upgrade from Jaunty to Karmic; S20privoxy exists in
/etc/rc{2345}.d/ linked to /etc/init.d/privoxy but does not start on
boot.
No error messages seen in daemon.log.
Scripts start Privoxy successfully when manually invoked.
--
privoxy not start at boot - karmic
https://bugs.launchpa
43 matches
Mail list logo
