update-manager does not correctly interpret gnome proxy configuration

Bug #173050 reported by Eduard Grebe on 2007-11-30
14
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

I am behind a firewall, but use an ubuntu mirror on the local network. Update-manager seems to ignore the automatic proxy configuration script (which should tell it to ignore the proxy for local addresses) and falls back upon the manual proxy configuration. (I know that it uses the manual config because I deliberately entered details of a separate proxy server in the manual fields to test this.) However, it also ignores the exclusion list entered under the "advanced" tab of the gnome proxy configuration dialogue.

This means the only way for me to bypass the proxy for the local mirror is to manually set gnome to use no proxy every time.

(BTW, the fact that there is no indication to the user that manual config is the fallback behaviour of apps that cannot use automatic config scripts is also rather confusing.)

sam tygier (samtygier) wrote :

a friends machine has an automatic proxy set up in system->preferences->network proxy.

update-manager claimed did not show the upgrade from gutsy to hardy, even after checking for updates, and using the -c -d flags. neither did the do-release-upgrade script.

there was no error message or warning.

after selecting 'direct connection to internet' (the machine only use the proxy so that it can access IP restricted services), the update-manager found the update.

Changed in update-manager:
status: New → Confirmed

I am still seeing this broken on Intrepid.

Any ETA on when this will be fixed?

This behavior is quite anti-social to one's local networking infrastructure, unnecessarily overloading HTTP proxy servers when proxying is supposed to be excepted for the provided apt servers.

Andreas Moog (ampelbein) on 2009-04-21
summary: update-manager does not correctly interpret gnome proxy configuration
- [gutsy]
Claus Frein (cfrein) wrote :

Same issue for me. Tested on jaunty.

I'd guess it's a problem for a lot of workstations/desktops in companies, which usually have internet-access only through a proxy and an internal apt-mirror for ubuntu-updates.

RedSingularity (redsingularity) wrote :

Cleaning up. Is this still an issue in the current stable release?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers