(see related bug on redhat bugzilla - https://bugzilla.redhat.com/show_bug.cgi?id=724948 )

When I enter proxy settings in nm, they are gone next time I look, also system does not use them.


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.


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


If you need testing, screenshots, vids, whatever just yell and I will be happy to help.