This still exists in Hardy.
Proxy is set in both Gnome and APT. FFx works perfectly, command line apt or
Synaptic Package Manager and Update-Manager fail to connect to the proxy.
W: Failed to fetch
Please set the importance of this bug much higher than it currently is.
This bug is preventing me from upgrading from Gutsy to Hardy, because
for bandwidth reasons I have to use apt-cacher.
Note, though, that update-manager should follow APT's proxy settings,
not GNOME's settings.
--
Doesn't
I have had a similar problem during a Feisty to Gutsy upgrade using apt-
cacher as proxy (see https://bugs.launchpad.net/ubuntu/+source/update-
manager/+bug/113658 ), but it's a generic proxy problem. If Canonical
are serious about the corporate market, where proxy servers are very
common, they
I agree with Richard: bug #113658 is related to this.
Also people here at my university lab (where we use apt-cacher to save
bandwith) would benefit a lot!
(p.s. Richard: put # before the bug number, in order to have automatic
linking ;) )
--
Doesn't honor gnome proxy settigs
Unsetting http_proxy solved the problem in gutsy also. This problem
persits since edgy. Why is it not solved yet?
--
Doesn't honor gnome proxy settigs
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
I still don't think that the gnome proxy settings should be what update-
manager should look at for several reasons:
1. I might run update-manager with root permissions (remember: I might even do
this without a proper intention, because all the update tools need superuser
priviliges) - then
I think I know what is going on here. When you set the proxy settings in
your Gnome Preferences, it does two different things:
- Sets the /system/http_proxy gconf keys
- Sets the $http_proxy environment variable.
It appears to be the second of these that is causing the problem (at
