Bug 724948

I have the same in F16 Alpha. 

This is similar (I would say the same) as 691627

Drewe

I think the problem is deeper than this - I can get my settings to stick using the command line, but it still does not use the proxy setting. My output is 


gsettings list-recursively org.gnome.system.proxy
org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8']
org.gnome.system.proxy mode 'manual'
org.gnome.system.proxy use-same-proxy false
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled true
org.gnome.system.proxy.http host 'tmproxy'
org.gnome.system.proxy.http port 8080
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.socks host ''
org.gnome.system.proxy.socks port 0


Which is the correct proxy and port, and enabled is true. But if I do a proxy test (for example http://www.lagado.com/proxy-test), I am going without a proxy (I can tell by IP's - the proxy has a different exit point).

If I manually set an app (say firefox) to the proxy it works - but I cannot set system wide.

For further information - I did a bunch of testing with fenrus02 on the #fedora-qa Channel.

Firefox can use the proxy ok, when it is set manually inside firefox. Same for xchat.

Proxy will not take system wide through network manager. 

I set http_proxy variables, and they echo correctly, does not use proxy.
[drewe@techpcl ~]$ echo $http_proxy
http://tmproxy:8080/

I used dconf-editor to manually force the proxy settings - does not use proxy, and as soon as you load the network manager the proxy is overwritten to not in use and all values in http_proxy are lost. (the port however isn't, nor is HTTPS_proxy lost)

I can see, ping, etc my proxy (as noted, I can use it application based - xchat and firefox are using with app based settings).


I have F15/F16 boxes here if more testing is needed, and a couple of spare (large) esxi hosts to do clean loads if required - more than happy to help if someone wants more testing done.

(also, this is listed as an F15 bug, I am testing the same issues in F16, possibly create a new linked bug report or update this?)

Drewe

(apologies to all who keep getting CC'ed). 

I've created a bug on the gnome bugzilla, as it appears to be a network manager bug, though I lack the specific skills\knowledge to confirm - 

https://bugzilla.gnome.org/show_bug.cgi?id=659909

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping