update-manager connects to obsolete proxy

Bug #183750 reported by ErikH on 2008-01-17
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

My computer (using hardy/8.04) sometimes is located behind
a proxy, sometimes not.

My problem is that I cannot use update-manager anymore because
it insists on using the proxy. I have unconfigured the proxy
in System->Preferences->Network Proxy. In Synaptics
a direct connection is configured and also apt-get works without
proxy problems.
But update-manager always reports
Failed to fetch http://de.archive.ubuntu.com/ ...
Could not connect to proxy_ip:proxy_port (proxy_ip). - connect (113 No route to host).

Problems for me:
1) It is not clear for me where update-manager gets its proxy data from.
2) There is no command line parameter to disable proxy use

Erik

Alfred Schwarz (fredl) wrote :

I also noticed a related problem that update-manager has with proxy-settings.
I'm using approx for package-caching on a central server and therefore have specialized sources.list files on my clients. On my Laptop I have Hardy installed, apt is configured correctly and manual invocations of it work perfectly, as does synaptic.
Only the update-manager insists on connecting to my approx server via port 3128, but I cannot find out where it gets this idea from. $HTTP_PROXY is empty, and the only application that even knows about squid running on the same server, is Firefox. Of course, as soon as I stop squid there, update-manager here fails and reports a refused connection.
Since I couldn't find out why it always tries port 3128 (or even tries to use a proxy at all), I even purged and freshly installed the package, but still the same behaviour.

After all I found a very interesting solution:
Synaptic offers an option to activate and configure a proxy. Of course the settings were empty and disabled, but I intentionally filled in the settings for my squid (same server as approx, but port 3128), clicked on "accept" and immediately afterwards changed this setting to "direct connection" again. Clicked on "Accept" once more and voila, update-manager connected correctly via port 9999...

So I suppose it's rather a bug in Synaptic than in update-manager which obviously takes this information somewhere from synaptic. Strange though, that synaptic itself must have kept this setting from sometimes earlier, but did not use it in this wrong way anymore.

Best Regards,
Fredl.

andy_w (andyw-adsl4less) wrote :

Hi Fredl,

I'd had exactly the same problem, now fixed thanks to your efforts above.

As a newbie I won't even ask how you worked that one out, but it's the results that count!

Regards,

Andyw.

Michele Mangili (mangilimic) wrote :

I'm moving this report since it seems that this bug belongs to synaptic, not update-manager.

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in update-manager:
status: New → Confirmed
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 283500, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

itopia (jjt) wrote :

I had this same problem specifically with update manager in version 9.10 Ubuntu. Under System->preferences->network proxy saw it had 2 locations. Deleted the location with the proxy and that then allowed update manager to update not using the proxy.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers