Description of problem: If the "Use the same proxy for all protocols" checkbox is checked *before* the HTTP proxy information is entered, blank proxy configuration is propagated to non-HTTP proxies. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Run 'gnome-network-properties' 2. Select "Manual proxy configuration" 3. Check "Use the same proxy for all protocols" 4. Enter 'proxy.bugreport.org' and '1234' in 'HTTP proxy' and 'Port', respectively 5. Click "Close" 6. Run 'gconftool-2 -a /system/proxy' Actual results: ftp_host = secure_host = secure_port = 0 socks_host = socks_port = 0 ftp_port = 0 Expected results: ftp_host = proxy.bugreport.org secure_host = proxy.bugreport.org secure_port = 1234 socks_host = proxy.bugreport.org socks_port = 1234 ftp_port = 1234 Additional info: If the "Use the same proxy for all protocols" checkbox is checked *after* you enter your HTTP proxy information, you get the correct results. This problem is severe in that it causes HTTPS traffic (and FTP and socket, for that matter) to fail.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixing component - was incorrectly categorized.
The values of the other fields shouldn't matter because the application should check "/system/http_proxy/use_same_proxy" and use the http proxy if that's true, and the protocol specific one if it's false.
In that case, this would be a bug in Sun's JRE, because it was the "java.net.useSystemProxies" behavior that was failing. If this is the final word, then this bug can be resolved as "not a bug"
However, I will note that the disparity between the population of those fields depending on whether you check the checkbox before or after you fill out the HTTP proxy info is disconcerting. Perhaps, just to be safe, the fields should be set to that the of the HTTP proxy field regardless...?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.