USE Flag pgo enabled. if http_proxy is set firefox can't connecting to the URL http://localhost:8888/index.html ( obj-x86_64-unknown-linux-gnu/_profile/pgo/profileserver.py ). unset the env in the ebuild: --- /usr/portage/www-client/firefox/firefox-10.0.4.ebuild.orig 2012-05-13 13:10:25.000000000 +0200 +++ /usr/portage/www-client/firefox/firefox-10.0.4.ebuild 2012-05-13 16:34:52.000000000 +0200 @@ -103,7 +103,10 @@ pkg_setup() { ORBIT_SOCKETDIR \ SESSION_MANAGER \ XDG_SESSION_COOKIE \ - XAUTHORITY + XAUTHORITY \ + http_proxy \ + HTTP_proxy \ + HTTP_PROXY if ! use bindist; then einfo
http_proxy must be unset in the pkg_compile function, not in pkg_setup. I compiled Firefox with useflag pgo and this patch: --- firefox-10.0.4.ebuild?revision=1.5 2012-05-13 19:59:08.000000000 +0200 +++ firefox-10.0.4.ebuild 2012-05-13 20:00:51.000000000 +0200 @@ -228,6 +228,10 @@ src_compile() { if use pgo; then addpredict /root addpredict /etc/gconf + + # unset http_proxy - bug 415753 + unset http_proxy + # Reset and cleanup environment variables used by GNOME/XDG gnome2_environment_reset
I just encountered this myself, with www-client/firefox-10.0.5. My symptom? A Firefox window in my running X session, showing an error emitted by my proxy server about connecting to localhost:8888.
PGO useflag has been masked until such a time we can properly support it in gentoo. Soon as we can we will unmask and support pgo builds for all users. At this time even upstream is having problems supporting pgo builds in Linux. I will continue to track there upstream to determine when best we can come back and review all pgo build failures. Please ignore resolution we no longer have an option for later.
