Comment 4 for bug 702898

Marking the bug as public.

Apparently the issue happens when the GeoIP server returns None instead of the location.

Playing with routes at the office, going out from Nuremberg gives:
<?xml version="1.0" encoding="UTF-8"?><Response><Ip>78.46.20.84</Ip><Status>OK</Status><CountryCode>DE</CountryCode><CountryCode3>DEU</CountryCode3><CountryName>Germany</CountryName><RegionCode>None</RegionCode><RegionName>None</RegionName><City>None</City><ZipPostalCode></ZipPostalCode><Latitude>51.0000</Latitude><Longitude>9.0000</Longitude><AreaCode>0</AreaCode><TimeZone>Europe/Berlin</TimeZone></Response>

The same from a Sherbrooke, QC IP that's not in Maxmind's database yet:
<?xml version="1.0" encoding="UTF-8"?><Response><Ip>74.114.101.94</Ip><Status>OK</Status><CountryCode>CA</CountryCode><CountryCode3>CAN</CountryCode3><CountryName>Canada</CountryName><RegionCode>None</RegionCode><RegionName>None</RegionName><City>None</City><ZipPostalCode></ZipPostalCode><Latitude>60.0000</Latitude><Longitude>-95.0000</Longitude><AreaCode>0</AreaCode><TimeZone>None</TimeZone></Response>

The first works fine, the second crashes.

That was tested by doing: wget -O - -q http://geoip.ubuntu.com/lookup