update-manager crashed with InvalidURL in _set_hostport()

[Chris Fleming]

Binary package hint: update-manager

Whenever I run Update manager, I get the error "Update Manager closed unexpectedly" around 3 times.

If I hit close, then the GUI does seem to allow me to install updates.

This problem only started after I upgraded to hardy.

I am accessing the internet through a proxy server, if this makes any difference.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.5
Package: update-manager 1:0.93.23
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with InvalidURL in _set_hostport()
Uname: Linux 2.6.24-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev scanner tape video

[Chris Fleming (chrisfleming)]

Looking at the traceback, it looks to me like this may be caused by the proxy setting.

Currently I have a proxy configured with gnome network preference settings as:
host: web-proxy.britain.agilent.com
port: 8088

[Michael Vogt (mvo)]

Thanks for your bugreport.

Could you please open gnome-terminal and post the output of:
$ echo $http_proxy

thanks,
 Michael

[Michael Vogt (mvo)]

I can reproduce it here with:
$ http_proxy=http://proxy:/ update-manager

[Chris Fleming (chrisfleming)]

annoyingly, I did this check:
echo $http_proxy
http://web-proxy.britain.agilent.com:8088/

However today when I ran update manager I didn't see the error!

As far as I know, I've not changed anything since I saw this yesterday. But will keep an eye out.

[Michael Vogt (mvo)]

@Chris: thanks for testing it. that is strange indeed. let me know if it appears again please.

[Chris Fleming (chrisfleming)]

The game is back on. Saw the "usual" crash message when I ran update manager this morning. Furthermore, when I get to the point where I can try and install updates, I get the error:

W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/pool/main/f/foomatic-filters/foomatic-filters_4.0.0~bzr177-0ubuntu1_i386.deb
  Could not resolve ‘http’

Networking and proxy settings seem good for everything else. No changes apart from a reboot since yesterday's problem:

echo $http_proxy
http://web-proxy.britain.agilent.com:8088/

(not sure of the etiquette regarding status at this stage. Changing back to New, possibly should go to in progrss or maybe I should just leave this as is... )

[Chris Fleming (chrisfleming)]

After some more digging around, it looks like this is a proxy config issue. I found that apt proxy setting was completly wonky:

cat /etc/apt/apt.conf
Acquire::http::Proxy "http://http://web-proxy.britain.agilent.com/:8088/";

If I delete or fix this then everything is okay.

I *think* this must have been automagically set by something when I first installed Hardy on my PC.

The only question is should the update manager check that the source it's using for proxy information is in the correct format before deciding to use it?

[Jean-Baptiste Lallement (jibel)]

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.

update-manager should not break even if proxy setting are wrong. low priority because the user need to enter wrong settings in /etc/apt/apt.conf in order to trigger this bug. The cause if the change in Chris's config is another story.

Thanks for taking the time to make Ubuntu better!