The "use the same proxy for all protocols" functionality under the gnome network preferences doesn't work under certain conditions.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center |
Fix Released
|
Medium
|
|||
gnome-control-center (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
The "use the same proxy for all protocols" functionality under the gnome network preferences doesn't work under certain conditions.
Requirements
- You need to be inside a netowrk that requires two proxy servers. The proxy servers should use (preferably NTLM) authentication.
Steps to reproduce
- System-
- Select "manual proxy configuration"
- Enter a proxy name inside the HTTP proxy edit box (say proxy A) and click "use the same proxy for all protocols"
- notice that the remaining edit boxes get disabled and also get populated with the proxy name entered for HTTP
- Now change the proxy name inside the HTTP proxy (say to proxy B).
- Notice that the old proxy name remains inside the other edit boxes (this is bug 1). The only way to repopulate the new proxy name in the disabled edit boxes is to uncheck and check the "use the same proxy for all protocols" box again.
- Click close
- Open Galeon browser and access a HTTPS location (say https:/
- Notice that the browser shows a pop up dialog box asking for authentication. However the proxy name mentioned on the top of the dialog box is the old proxy name (proxy A) instead of the new one (proxy B) (this is bug 2).
$ uname -a
Linux lap432 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
Changed in gnome-control-center: | |
assignee: | nobody → desktop-bugs |
importance: | Undecided → Low |
Changed in gnome-control-center: | |
assignee: | desktop-bugs → mvo |
Changed in gnome-control-center (Ubuntu): | |
assignee: | Michael Vogt (mvo) → nobody |
status: | New → Confirmed |
Changed in gnome-control-center: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.