[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2009-06-18 Thread Kaushalya
*** This bug is a duplicate of bug 13661 *** https://bugs.launchpad.net/bugs/13661 This bug wasted a whole day. It is not fixed in 8.10. I've changed network proxy as direct connection. But update-manager tries to connect to a proxy which was configured earlier, and says it can't connect to

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2009-05-23 Thread afrodeity
*** This bug is a duplicate of bug 13661 *** https://bugs.launchpad.net/bugs/13661 Extremely annoying, irritating and time-wasting bug that should be fixed as an update in Hardy. I don't see any reason to perpetuate the suffering of users who expect at least a smoother ride with update

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2008-10-08 Thread Lionel Dricot
*** This bug is a duplicate of bug 13661 *** https://bugs.launchpad.net/bugs/13661 ** This bug has been marked a duplicate of bug 13661 get proxy via gconf -- Update Manager and synaptic HTTP Proxy settings https://bugs.launchpad.net/bugs/21536 You received this bug notification because

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2008-05-14 Thread Brian Pitts
Has the behavior of update manager changed? Here's my experience with it: During normal use, update-manager uses the proxy set in Synaptic. During the upgrade to a new Ubuntu release, update-manager does not use the proxy set in Synaptic. It uses it initially (e.g the download of

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2007-11-22 Thread Pik Master
Very annoying, I could not upgrade from feisty to gutsy (7.04 - 7.10) and I could not find a reason. Additionaly, id does not honor the automatic configuration URL (PAC file), nor has the option to autodetect network settings (but this is an error for gnome-network-manager). Please, make the

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2007-09-28 Thread betchern0t
The behaviour on feisty that I see is that it half uses the proxy settings in gnome. It ignores the ignore local addresses settings but still attempts to use the proxy settings. Hard coding proxy credentials although a common solution should be frowned upon. Since I have the proxy set to use the

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2007-04-18 Thread Michael Vogt
** This bug is no longer a duplicate of bug 13661 get proxy via gconf ** Changed in: update-manager (Ubuntu) Target: None = later -- Update Manager and synaptic HTTP Proxy settings https://bugs.launchpad.net/bugs/21536 You received this bug notification because you are a member of

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2007-04-13 Thread Jeff Rasmussen
*** This bug is a duplicate of bug 13661 *** https://bugs.launchpad.net/bugs/13661 I ran into the same problem. Update-manager should at least use apt.conf proxy settings and then we can give users a APT-proxy gui tool. A workaround is to run gksu gnome-network-preferences. We could add a

[Bug 21536] Re: Update Manager and synaptic HTTP Proxy settings

2007-04-13 Thread Jeff Rasmussen
*** This bug is a duplicate of bug 13661 *** https://bugs.launchpad.net/bugs/13661 I think we can confirm this bug and keep it as a wishlist importance ** Changed in: update-manager (Ubuntu) Status: Unconfirmed = Confirmed -- Update Manager and synaptic HTTP Proxy settings