Bug#644373: libproxy0 0.3.1-3 doesn't work with automatic proxy configuration

Laurent Bigonville bigon at debian.org
Sat Sep 20 14:51:19 UTC 2014


Le Sat, 20 Sep 2014 15:32:16 +0200,
Petter Reinholdtsen <pere at hungry.com> a écrit :

> [Laurent Bigonville 2014-08-24]
> > On Jessie/unstable, do you have libproxy1-plugin-mozjs or
> > libproxy1-plugin-webkit installed?
> 
> [Petter Reinholdtsen 2014-08-25]
> > As far as I can tell from the strace output and the web server log,
> > the proxy program do not try to connect to the web server at all.
> 
> This is how I check:
> 
> root at pxe-test6-pre:~/dpkg-1.17.13# dpkg -l libproxy*
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/
> Name                          Version      Architecture Description
> +++-=============================-============-============-================================================================
> ii  libproxy-tools                0.4.11-4     amd64        automatic
> proxy configuration management library (tools) ii
> libproxy1:amd64               0.4.11-4     amd64        automatic
> proxy configuration management library (shared) ii
> libproxy1-plugin-webkit:amd64 0.4.11-4     amd64        automatic
> proxy configuration management library (Webkit plugin)
> root at pxe-test6-pre:~/dpkg-1.17.13# echo http://www.debian.org/
> |strace proxy 2>&1|grep connect connect(3, {sa_family=AF_LOCAL,
> sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or
> directory) connect(3, {sa_family=AF_LOCAL,
> sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or
> directory) root at pxe-test6-pre:~/dpkg-1.17.13# GET
> http://wpad/wpad.dat function FindProxyForURL(url, host) { return
> "DIRECT"; } root at pxe-test6-pre:~/dpkg-1.17.13# 
> 
> As you can see, strace show no connect to the web server, even if the
> libproxy1-plugin-webkit package is installed.
> 

You should probably also install libproxy1-plugin-gsettings and/or
libproxy1-plugin-networkmanager so libproxy knows about the
configuration of the proxy




More information about the pkg-gnome-maintainers mailing list