Description of problem: Version-Release number of selected component (if applicable): 2.6.38.2-9.fc15.x86_64 gnome-shell-3.0.0.2-2.fc15.x86_64 How reproducible: Steps to Reproduce: 1. Install Fedora 15 beta default Desktop installation. 2. Try set network proxy via "Network Settings (top panel/bar) - Network proxy". 3. Test network to see if the proxy works. Actual results: The proxy settings does not have any effects - not work. Expected results: Should be work if defined. Additional info: In fedora 14 (and previous versions) the Gnome network proxy worked fine.
I was about to file the same bug. Running Privoxy locally, it is simply ignored by both Firefox and Epiphany. (Checked by loading http://config.privoxy.org/ which should be intercepted if the proxy is working.)
Probably related to bug 691627.
That bug is for XULRunner, but this was raised because the proxy does not work in Desktop environment (including terminal) in general.
What specific programs are you using that are not respecting the proxy settings? The control panel is setting the proxy settings correctly, but some programs may still be looking for them in the old (GNOME 2.x) location.
For example software updates does not work or if you try yum update/installs in the terminal. In Fedora 14 'env' command in terminal shows that http_proxy/https_proxy is set. In fedora 15, it does not set these variables.
Ah, gnome-terminal is still looking in GConf for the proxy settings. There's a patch upstream. We should be able to get this into GNOME 3.0.1 and into F15 from there.
(In reply to comment #6) > Ah, gnome-terminal is still looking in GConf for the proxy settings. There's a > patch upstream. We should be able to get this into GNOME 3.0.1 and into F15 > from there. Like I said in comment #1, the problem also affects browsers such as Epiphany and Firefox as well as Chromium.
Epiphany should not be affected if you have libsoup >= 2.33.92 and glib-networking >= 2.28.4. If it is, that's a separate bug. Firefox is 691627. Chromium would be yet another bug. (The bug being "it's still looking in gconf rather than having been updated to look in gsettings".)