Traceback (most recent call last):
File "libappupdater\guiqt.pyo", line 973, in _action_options_triggered
File "libappupdater\guiqt.pyo", line 1632, in _load_config
File "libappupdater\core.pyo", line 607, in get_repos
File "libappupdater\core.pyo", line 574, in parse_repos
File "libappupdater\core.pyo", line 1016, in _download_xml
File "libappupdater\core.pyo", line 1042, in _do_download_xml
File "libappupdater\core.pyo", line 1225, in download_file
File "libappupdater\download.pyo", line 238, in get
File "libappupdater\download.pyo", line 704, in download_metalink
File "libappupdater\download.pyo", line 594, in parse_metalink
File "libappupdater\download.pyo", line 200, in urlhead
File "urllib2.pyo", line 126, in urlopen
File "urllib2.pyo", line 391, in open
File "urllib2.pyo", line 409, in _open
File "urllib2.pyo", line 369, in _call_chain
File "urllib2.pyo", line 1170, in http_open
File "libappupdater\proxy.pyo", line 279, in do_open
File "urllib2.pyo", line 1145, in do_open
URLError: <urlopen error [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond>
This could be because Appupdater isn't reading the proxy from the registry correctly.
In particular this is probably not reading the registry settings correctly on x64 systems.
This is not just a x64 issue, see ID: 3611737. This is probably just a generic crash when a proxy is required but not found. It might not be found because of a .pac or script file or x64 registry key.
"Appupdater is supposed to detect your proxy settings from the registry.
Unfortunately this doesn't work if you are using a script (.pac) file for
configuration, is that your case?"
No, the users just have to enter proxy settings manually for each application they need (it's a small office).
Fixed in svn r1047. download_file now catches urllib2.URLError