The current epiphany fails to load exterenal web sites behind our proxy: rose@moose:/home/rose/Txt(58)$ env | grep -i proxy PROXY=http://10.101.10.254:3128 NO_PROXY=localhost,127.0.0.0/8,192.168.2.0/8 http_proxy=http://10.101.10.254:3128 FTP_PROXY=http://10.101.10.254:3128 ftp_proxy=http://10.101.10.254:3128 ALL_PROXY=socks://10.101.10.254:3128/ all_proxy=socks://10.101.10.254:3128/ additionalparam=-J-DproxyHost=10.101.10.254 -J-DproxyPort=3128 HTTPS_PROXY=http://10.101.10.254:3128 https_proxy=https://10.101.10.254:3128/ no_proxy=localhost,127.0.0.0/8,192.168.2.0/8 HTTP_PROXY=http://10.101.10.254:3128 rose@moose:/home/rose/Txt(59)$ epiphany --version Webbrowser 2.30.2 rose@moose:/home/rose/Txt(60)$ qlist -Iv epiphany www-client/epiphany-2.30.2-r1 www-client/epiphany-extensions-2.30.1 If I start epiphany I get: Unable to load page Problem occurred while loading the URL http://www.google.com/ Cannot connect to destination Reproducible: Always
Please post the output of "emerge -pv net-libs/libproxy net-libs/libsoup" Try with net-libs/libproxy-0.2* and 0.4* versions
Also be sure you have set your proxy from gnome-network-properties
I have System->Settings->Network-Proxy->Manual Proxy-Configuration->Use the same proxy for all protocolls -> HTTP-Proxy: 10.101.10.254 Port: 3128 (translated from my german menue) root@moose:/root(23)# genlop -t libproxy | tail Tue May 11 02:58:21 2010 >>> net-libs/libproxy-0.2.3-r3 merge time: 38 seconds. Wed May 19 04:38:02 2010 >>> net-libs/libproxy-0.4.1 merge time: 33 seconds. Sat May 22 04:26:04 2010 >>> net-libs/libproxy-0.4.2 merge time: 22 seconds. root@moose:/root(24)# genlop -t epiphany | tail Wed Jun 16 13:04:44 2010 >>> www-client/epiphany-2.30.2 merge time: 45 seconds. Tue Jul 6 04:23:18 2010 >>> www-client/epiphany-2.30.2-r1 merge time: 56 seconds. Thu Jul 8 17:30:10 2010 >>> www-client/epiphany-2.30.2-r1 merge time: 1 minute and 3 seconds. I.e., epiphany should be compiled with libproxy-0.4.2. root@moose:/root(25)# emerge -pv net-libs/libproxy net-libs/libsoup These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-libs/libproxy-0.4.2 USE="gnome networkmanager perl python webkit xulrunner -debug -kde -vala" 0 kB [ebuild R ] net-libs/libsoup-2.30.2-r1 USE="doc gnome ssl -debug (-introspection)" 0 kB If I start /usr/bin/gnome-network-properties, I see the same settings as under the System->Settings-> menue. So I will downgrade libproxy as the next step.
After downgrading libproxy root@moose:/root(31)# emerge -C epiphany libsoup-gnome && emerge -v1 =libproxy-0.2.3-r3 && emerge -v1 epiphany epiphany works behind our proxy again.
Is this a regression over www-client/epiphany-2.30.2 ?
(In reply to comment #4) > After downgrading libproxy > root@moose:/root(31)# emerge -C epiphany libsoup-gnome && emerge -v1 > =libproxy-0.2.3-r3 && emerge -v1 epiphany > > epiphany works behind our proxy again. > Then it's a problem with newer libproxy (!)
Did you follow update rules logged when updating libproxy?
If I emerge libroxy: root@moose:/root(38)# emerge -C epiphany libsoup-gnome libproxy && emerge -v1 libsoup-gnome ... These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-libs/libproxy-0.4.2 USE="gnome networkmanager perl python webkit xulrunner -debug -kde -vala" 0 kB [ebuild N ] net-libs/libsoup-gnome-2.30.2 USE="doc -debug (-introspection)" 0 kB ... >>> Installing (1 of 2) net-libs/libproxy-0.4.2 * checking 22 files for package collisions --- /usr/ --- /usr/bin/ >>> /usr/bin/proxy --- /usr/lib64/ --- /usr/lib64/perl5/ --- /usr/lib64/perl5/vendor_perl/ --- /usr/lib64/perl5/vendor_perl/5.10.1/ --- /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/ --- /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/Net/ >>> /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/Net/Libproxy.pm --- /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/auto/ --- /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/auto/Net/ >>> /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/auto/Net/Libproxy/ >>> /usr/lib64/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/auto/Net/Libproxy/Libproxy.so >>> /usr/lib64/libproxy.so.1.0.0 >>> /usr/lib64/libproxy.so.1 -> libproxy.so.1.0.0 --- /usr/lib64/pkgconfig/ >>> /usr/lib64/pkgconfig/libproxy-1.0.pc >>> /usr/lib64/libproxy.so -> libproxy.so.1 >>> /usr/lib64/libmodman.so.0 --- /usr/lib64/python2.6/ --- /usr/lib64/python2.6/site-packages/ >>> /usr/lib64/python2.6/site-packages/libproxy.py >>> /usr/lib64/libproxy/ >>> /usr/lib64/libproxy/0.4.2/ >>> /usr/lib64/libproxy/0.4.2/modules/ >>> /usr/lib64/libproxy/0.4.2/modules/pacrunner_mozjs.so >>> /usr/lib64/libproxy/0.4.2/modules/config_gnome.so >>> /usr/lib64/libproxy/0.4.2/modules/network_networkmanager.so >>> /usr/lib64/libproxy/0.4.2/modules/pacrunner_webkit.so >>> /usr/lib64/libmodman.so.0.0.0 -> libmodman.so.0 >>> /usr/lib64/libmodman.so -> libmodman.so.0.0.0 --- /usr/share/ --- /usr/share/doc/ >>> /usr/share/doc/libproxy-0.4.2/ >>> /usr/share/doc/libproxy-0.4.2/AUTHORS.bz2 >>> /usr/share/doc/libproxy-0.4.2/NEWS.bz2 >>> /usr/share/doc/libproxy-0.4.2/README.bz2 >>> /usr/share/doc/libproxy-0.4.2/ChangeLog.bz2 --- /usr/share/cmake/ --- /usr/share/cmake/Modules/ >>> /usr/share/cmake/Modules/Findlibproxy.cmake --- /usr/libexec/ >>> /usr/libexec/pxgconf --- /usr/include/ >>> /usr/include/proxy.h * Compilation and optimization of Python modules for CPython 2.6 ... [ ok ] >>> Regenerating /etc/ld.so.cache... >>> Emerging (2 of 2) net-libs/libsoup-gnome-2.30.2 I don't see any hint about update rules. Neither the elogviewer shows any entry about libproxy.
Please post "ls -l /usr/lib64/libproxy.so*" output
root@moose:/root(3)# ls -l /usr/lib64/libproxy.so* lrwxrwxrwx 1 root root 13 2010-07-09 17:28 /usr/lib64/libproxy.so -> libproxy.so.1 lrwxrwxrwx 1 root root 17 2010-07-09 17:28 /usr/lib64/libproxy.so.1 -> libproxy.so.1.0.0 -rwxr-xr-x 1 root root 117952 2010-07-09 17:28 /usr/lib64/libproxy.so.1.0.0
Looks normal :-(
works just fine here (at least with epiphany-2.30.5).
One year later I still have the same issues with libproxy-0.4.6-r3 and epiphany-2.30.6-r1: rose@moose:/home/rose(1)$ env | grep -i proxy NO_PROXY=localhost,127.0.0.0/8 http_proxy=http://10.101.10.254:3128 FTP_PROXY=http://10.101.10.254:3128 ftp_proxy=http://10.101.10.254:3128 all_proxy=socks://10.101.10.254:3128/ ALL_PROXY=socks://10.101.10.254:3128/ https_proxy=http://10.101.10.254:3128/ HTTPS_PROXY=http://10.101.10.254:3128 no_proxy=localhost,127.0.0.0/8 HTTP_PROXY=http://10.101.10.254:3128 rose@moose:/home/rose(2)$ /usr/bin/gnome-network-properties shows correct proxy settings. rose@moose:/home/rose(20)$ gconftool-2 -a /system/proxy old_ftp_host = old_ftp_port = 0 secure_host = 10.101.10.254 secure_port = 3128 mode = manual autoconfig_url = old_secure_port = 0 old_secure_host = old_socks_port = 0 old_socks_host = ftp_host = 10.101.10.254 socks_host = 10.101.10.254 ftp_port = 3128 socks_port = 3128 rose@moose:/home/rose(21)$ gconftool-2 -a /system/http_proxy use_http_proxy = true authentication_password = host = 10.101.10.254 port = 3128 use_authentication = false ignore_hosts = [localhost,127.0.0.0/8] use_same_proxy = true authentication_user = rose@moose:/home/rose(5)$ wget http://www.google.com --2011-10-11 12:20:15-- http://www.google.com/ Verbindungsaufbau zu 10.101.10.254:3128... verbunden. Proxy-Anforderung gesendet, warte auf Antwort... 302 Moved Temporarily Platz: http://www.google.de/[folge] --2011-10-11 12:20:15-- http://www.google.de/ Wiederverwendung der bestehenden Verbindung zu 10.101.10.254:3128. Proxy-Anforderung gesendet, warte auf Antwort... 200 OK Länge: nicht spezifiziert [text/html] In »»index.html.1«« speichern. [ <=> ] 10,413 --.-K/s in 0.02s 2011-10-11 12:20:15 (591 KB/s) - »»index.html.1«« gespeichert [10413] I.e., wget works through the Proxy. Firefox works too, but epiphany hangs. I checked this on three systems.
Epiphany tries to access the site several minutes and then it shows: Cannot connect to destination (www.google.com)
It still works ok for me, Have you tried on a new created user account? (the main problem here is that upstream won't care about epiphany-2 :S)
I just created a new user "rose_testepi" and tried again. I am getting a little bit more debug information but I can't reach www.google.com amd any other http server outside our firewall: rose_testepi@cheetah ~ $ epiphany debug1: client_input_channel_open: ctype x11 rchan 3 win 87380 max 16384 debug1: client_request_x11: request from 127.0.0.1 41322 debug1: channel 1: new [x11] debug1: confirm x11 debug1: client_input_channel_open: ctype x11 rchan 4 win 87380 max 16384 debug1: client_request_x11: request from 127.0.0.1 41323 debug1: channel 2: new [x11] debug1: confirm x11 debug1: client_input_channel_open: ctype x11 rchan 5 win 87380 max 16384 debug1: client_request_x11: request from 127.0.0.1 41324 debug1: channel 3: new [x11] debug1: confirm x11 debug1: client_input_channel_open: ctype x11 rchan 6 win 87380 max 16384 debug1: client_request_x11: request from 127.0.0.1 41325 debug1: channel 4: new [x11] debug1: confirm x11 debug1: channel 4: FORCE input drain debug1: channel 4: free: x11, nchannels 5 debug1: client_input_channel_open: ctype x11 rchan 6 win 87380 max 16384 debug1: client_request_x11: request from 127.0.0.1 41326 debug1: channel 4: new [x11] debug1: confirm x11 debug1: channel 4: FORCE input drain debug1: channel 4: free: x11, nchannels 5 It is not a sever problem, because I have firefox as an alternative. But sometimes it is good to have second browser and epiphany is automatically installed as the default browser. I have also konqueror, but it starts too many processes and it makes too much noise if it is started: ... kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-font-vfont.xml" in xdgdata-mime kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-cpio.xml" in xdgdata-mime kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-cd-image.xml" in xdgdata-mime kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-gnome-saved-search.xml" in xdgdata-mime kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-machine-config.xml" in xdgdata-mime kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-lzma.xml" in xdgdata-mime kbuildsycoca4(20448) KBuildSycoca::createEntry: modified: "application/x-e-theme.xml" in xdgdata-mime ... kbuildsycoca4(20448) KBuildServiceFactory::populateServiceTypes: "/usr/share/applications/banshee.desktop" specifies undefined mimetype/servicetype "video/x-flc" kbuildsycoca4(20448) KBuildServiceFactory::populateServiceTypes: "/usr/share/applications/banshee.desktop" specifies undefined mimetype/servicetype "video/x-mpeg" kbuildsycoca4(20448) KBuildServiceFactory::populateServiceTypes: "/usr/share/applications/banshee.desktop" specifies undefined mimetype/servicetype "video/x-mpg" kbuildsycoca4(20448) KBuildServiceFactory::populateServiceTypes: "/usr/share/applications/gqview.desktop" specifies undefined mimetype/servicetype "image/svg" ...
Would be nice to check with other browser relying on gnome proxy settings (I think firefox uses their own), but I don't remember what browser could you test :S
Just these days the google calender connection in evolution stopped working. I found that epiphany doesn't work either (I normally don't use it) because I'm behind a firewall and the gnome-network-properties proxy settings are not respected. I've got quite the same symptoms as Jürgen though I'm on ~x86. Note that it is easy to overlook this problem if direct traffic without the specified proxy works as well, because everything appears to function as expected... (net-libs/libproxy 0.4.7, www-client/epiphany 2.30.6-r1) Maybe the reason could be that I recently enabled the icu use flag? A problem to gnome settings could come through dev-libs/libxml2 then. Have to check...
Checked USE=-icu, makes no difference :-(
FYI: Solved both problems (with epiphany-2.30.6-r1 and evolution-2.32.3-r1 Google Calendar source) by using dconf-editor to place the correct settings in /system/proxy/. Current gnome-network-properties (gnome-control-center-2.32.1-r1) uses gconf, but apparently some software already gets the values from dconf. Sorry for the noise if this is obvious for everybody! Regards, Bernd
Yeah it's not really obvious. I remember we had some similar reports but I can't remember if this solution made it to an official doc.
Maybe this should be backported :-/ http://git.gnome.org/browse/gnome-control-center/commit/?id=2a5eca505ddf0b7023d18f0b96efb811c1532c3d
I am using now epiphany-3.2.1. I used dconf-editor to enter again my proxy settings for ftp, http and https. The PROXY environment variables are set for root and rose: root@moose:/root(2)# env | grep -i proxy http_proxy=http://10.101.10.254:3128 ftp_proxy=http://10.101.10.254:3128 FTP_PROXY=http://10.101.10.254:3128 HTTPS_PROXY=http://10.101.10.254:3128 HTTP_PROXY=http://10.101.10.254:3128 rose@moose:/home_moose/rose(1)$ env | grep -i proxy http_proxy=http://10.101.10.254:3128 FTP_PROXY=http://10.101.10.254:3128 ftp_proxy=http://10.101.10.254:3128 HTTPS_PROXY=http://10.101.10.254:3128 HTTP_PROXY=http://10.101.10.254:3128 All other programs pass the proxy but epiphany.
Regarding gnome2: looks like epiphany should take settings from libproxy: http://git.gnome.org/browse/epiphany/commit/?h=gnome-2-30&id=01b36dd4aeebac60076b1e8d28dd1181129939bd Looks like people was suffering this issue with libproxy-0.4.6-r3, have you tried with 0.4.7?
It looks, whether it would work now. At least my first attempt with "epiphany http://www.google.de" did not fail. But libproxy-0.4.7 is already installed since october: rose@moose:/home_moose/rose(4)$ genlop -t libproxy | tail Tue Sep 20 14:49:44 2011 >>> net-libs/libproxy-0.4.6-r3 merge time: 21 seconds. Wed Oct 12 18:49:52 2011 >>> net-libs/libproxy-0.4.6-r3 merge time: 14 seconds. Wed Oct 19 10:28:37 2011 >>> net-libs/libproxy-0.4.7 merge time: 15 seconds. and epiphany did fail end of november, as noted in comment 23.
Doesn't libproxy only use environment proxy variables when USE=-gnome?
Now it fails again with epiphany-3.2.1-r1. rose@wildcat:/home_wildcat/rose(13)$ genlop -t libproxy | tail Sat Jan 14 16:49:32 2012 >>> net-libs/libproxy-0.4.7 merge time: 21 seconds. Mon Jan 30 16:50:01 2012 >>> net-libs/libproxy-0.4.7 merge time: 17 seconds. Mon Jan 30 17:28:26 2012 >>> net-libs/libproxy-0.4.7 merge time: 17 seconds. rose@wildcat:/home_wildcat/rose(14)$ genlop -t epiphany | tail Mon Jan 2 08:23:12 2012 >>> www-client/epiphany-3.2.1 merge time: 1 minute and 39 seconds. Tue Jan 3 05:41:15 2012 >>> www-client/epiphany-3.2.1 merge time: 1 minute and 48 seconds. Mon Mar 5 18:26:06 2012 >>> www-client/epiphany-3.2.1-r1 merge time: 1 minute and 56 seconds. rose@wildcat:/home_wildcat/rose(15)$ env | grep -i proxy http_proxy=http://10.101.10.254:3128 FTP_PROXY=http://10.101.10.254:3128 ftp_proxy=http://10.101.10.254:3128 HTTPS_PROXY=http://10.101.10.254:3128 HTTP_PROXY=http://10.101.10.254:3128 rose@wildcat:/home_wildcat/rose(16)$ epiphany www.google.de fails with: (epiphany:3537): GLib-GObject-WARNING **: invalid (NULL) pointer instance (epiphany:3537): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed "Cannot connect to destination (www.google.de)" Any other programm (firefox, ping, ...) does not have difficulties to access outside IP addresses: rose@wildcat:/home_wildcat/rose(17)$ ping www.google.de PING www-cctld.l.google.com (173.194.69.94) 56(84) bytes of data. 64 bytes from bk-in-f94.1e100.net (173.194.69.94): icmp_req=1 ttl=47 time=3.56 ms 64 bytes from bk-in-f94.1e100.net (173.194.69.94): icmp_req=2 ttl=47 time=3.51 ms
Please check with libproxy-0.4.10 and epiphany-3.4.0
I have been looking into this problem and have found that it is not a bug in Epiphany at all. The underlying bug is, in fact, in the GIO proxy resolver functions of GLib. Whenever a program calls the proxy resolver it returns a proxy string of "http://direct", which Epiphany takes to be a definitive statement of proxyless access to the Internet. Consequently, Epiphany never uses a proxy unless one is lurking transparently. Moreover, Epiphany never calls libproxy.so, even though it loads the library. If we can get the GIO function fixed, Epiphany can stop using libroxy completely and thus reduce its memory requirements. [Worse still, libproxy has its own bugs in resolving proxy connections, but that should be irreleveant once GIO is fixed.] I shall upload a test case that demonstrates the bug in GIO.
Created attachment 342774 [details] A test program to show proxy resolver bugs. Run ./proxy_test <Some URI> to show that GIO always returns "http://direct".
This is solved in 3.8, and won't be solved in 2.32
