*** This bug is a duplicate of bug 361554 ***
https://bugs.launchpad.net/bugs/361554
** Branch linked: lp:ubuntu/update-manager
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Ok, I have changed to incomplete.
** Changed in: update-manager (Ubuntu)
Status: Fix Released = Incomplete
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Thanks Serge
I tried return True as described in comment 28
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/24250/comments/28
He is right, that this routine url_downloadable() is the cause of the issue.
By skipping straight over it, all is well.
Until there is a patch, I believe
*** This bug is a duplicate of bug 361554 ***
https://bugs.launchpad.net/bugs/361554
Ok, if u look at #361554 someone has proposed a fix.
Marking as duplicate
** This bug has been marked a duplicate of bug 361554
update-manager doesn't honor apt.conf Proxy setting
--
Doesn't honor
MetaRelease.py (the Python code that does the check) uses urllib2
directly, and doesn't use the apt/synaptic settings. Although urllib2
looks at the environment variables for proxy settings, sudo zaps these
for security reasons. I was able to make it work by using sudo -s to get
a root shell,
I have seen this as well. It seems only to be a problem when you click
on the 'Upgrade' button, when it does some checks before displaying the
Release Notes. I can verify this by starting update-manager with ports
80 and 443 blocked on the proxy server (ie, http and https forced
through the
Distribution upgrade, as noted above, ignores proxy settings from any
source I've tried (apt, env, gnome). This means normal package upgrades
work fine, but you are unable to use the 'Upgrade' button on Update
Manager.
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
See info in #440229
workaround:
edit /usr/lib/python2.5/site-packages/UpdateManager/Core/utils.py
and add a line return True atthe beginning of the downloadable
function:
##
def url_downloadable(uri, debug_func=None):
helper that checks if
I am trying to do a release upgrade to karmic from jaunty and have noticed it
does not honor proxy settings.
Currently, regular upgrades work, but the dist-upgrade is failing.
I am running from a non-privileged user prompt
sudo update-manager -d
In another terminal i have a tcpdump running.
The problem is that Synaptic caches the proxy settings in its config
file, and the Apply system wide option doesn't know how to replace
that (naturally).
Take a look in /root/.synaptic/synaptic.conf - I wager you will see the
old proxy settings. Either correct them there, or delete them so that
I just downloaded and installed Jaunty, the problem is still present.
Apparently it is possible to set the proxy, but never to change it back.
Apply system wide in the network proxy menu seems to not change a
thing for the update manager. Very annoying!
--
Doesn't honor gnome proxy settings
Actually there seem to be more issues. If the proxy is set once, it will
never be set back for the update manager, apt, synaptic, but ALSO for
totem, rythmbox, etc. Firefox does change itself along with the proxy
setting. It's like there is still a hidden setting active.
--
Doesn't honor gnome
ok, as Matt Mossholder wrote in 2007! (#13) the problem is that the
network proxy manager from gnome can set, but cannot unset the
http_proxy environmental variable. Only manual unset overrides it, and
firefox seems to not care?
Interestingly, if you use reset in the gnome network proxy manager,
I still got this problem in Jaunty. Any help appreciated.
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
This bug was fixed in the package update-manager - 1:0.97
---
update-manager (1:0.97) jaunty; urgency=low
* UpdateManager/Core/MetaRelease.py:
- remove debug message (LP: #310046)
* UpdateManager/Common/utils.py:
- when initializing the proxy configuration, do in this
Clarification question: Given that this is fixed in Jaunty (much thanks,
by the way), will it first apply to Intrepid = Jaunty upgrades, or
Jaunty = Jaunty+1 upgrades?
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a
I checked the way the proxy initialization works and I changed it so that it
now goes in the order of:
- apt proxy setting
- synaptic proxy setting
- gconf proxy setting
- http environemnt
(in bzr for jaunty). If there are still issues left, please file them as
seperate bugs because the original
** Tags added: qa-jaunty-foundations
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Summary changed:
- Doesn't honor gnome proxy settigs
+ Doesn't honor gnome proxy settings
--
Doesn't honor gnome proxy settings
https://bugs.launchpad.net/bugs/24250
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
19 matches
Mail list logo
