Time Zone selection shows about 20 different "New York"s and doesn't autoselect my location

Blank TZ map as described

So many New Yorks, so little time

Thanks for your report.

I can confirm with other cities like Paris. The list contains weird names (Lungsod ng Paris - Île-de-France, France ), wrong spelling (París - Paris - Île-de-France, France) - looks like a spanish spelling - and duplicates

http://geoname-lookup.ubuntu.com/?query=New%20York returns:
[{"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York borg", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "Lungsod ng New York", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }, {"name" : "New York kenti", "admin1" : "New York", "country" : "United States", "longitude" : "-74.005970", "latitude" : "40.714270" }]

I got many many identical entries for "Frankfurt" (Germany) today as well as for "Frankfurt (Oder)" in my installation of today's lubuntu i386.

Further, there were two entries for Omsk, Russia.

http://geoname-lookup.ubuntu.com/?query=Sao%20Paulo returns:

[{"name" : "Sao Paulo", "admin1" : "São Paulo", "country" : "Brazil", "longitude" : "-46.636110", "latitude" : "-23.547500" }, {"name" : "Sao Paulo", "admin1" : "São Paulo", "country" : "Brazil", "longitude" : "-46.636110", "latitude" : "-23.547500" }, {"name" : "Sao Paulo", "admin1" : "São Paulo", "country" : "Brazil", "longitude" : "-46.636110", "latitude" : "-23.547500" }, {"name" : "Sao Paulo", "admin1" : "São Paulo", "country" : "Brazil", "longitude" : "-46.636110", "latitude" : "-23.547500" }, {"name" : "Sao Paulo", "admin1" : "Amazonas", "country" : "Brazil", "longitude" : "-62.900000", "latitude" : "-7.233330" }, {"name" : "Sao Vicente de Paulo", "admin1" : "Rio de Janeiro", "country" : "Brazil", "longitude" : "-42.259720", "latitude" : "-22.724440" }]

The correct could be:

[{"name" : "Sao Paulo", "admin1" : "São Paulo", "country" : "Brazil", "longitude" : "-46.636110", "latitude" : "-23.547500" } , {"name" : "Sao Vicente de Paulo", "admin1" : "Rio de Janeiro", "country" : "Brazil", "longitude" : "-42.259720", "latitude" : "-22.724440" }]

There isn't 4 Sao Paulo city, and neither Sao Paulo in Amazonas!!! take a look in municipalities' list of Brazil:

http://pt.wikipedia.org/wiki/Anexo:Lista_de_munic%C3%ADpios_do_Brasil#S

Not entirely a duplicate: as indicated in bug 740884, the client may well need to filter the list returned by the server.

I don't understand... filter list that has many repeated localization? For me this bug is duplicate of bug 740884

This bug is on the installer. That bug is on the date and time
indicator.

Sorry about that, now I undertand.

the bug also affects quantal

I had 5 choices for Rome timezone during test of Precise 12.04.1 iso: http://cdimage.ubuntu.com/precise/daily-live/20120817.3/precise-desktop-amd64.iso.

Can the code that makes the query to geoname-lookup not uniquely identify them by latitude and longtitude?

This is not a bug in the installer, but in the data source, which is Ubuntu Geonames (linked bug task). The source for which appears to be lp:~ubuntu-geonames-hackers/ubuntu-geonames/trunk.

The source needs to be fixed to not include this duplicate info - that will correct the issue for all historical installer images as well.

Dmitrijs has volunteered to look at this.

The fix is committed in the sense of being available in the lp:ubuntu-geonames. It is still currently pending deployment. After it will be deployed, there will be 4 slightly different New Yorks instead of 20.

I get five choices for timezone Rome while testing this ISO: http://cdimage.ubuntu.com/daily-live/20120903.4/quantal-desktop-armhf+omap4.img on a Panda board.

I get five choices for timezone Rome while testing this ISO: http://cdimage.ubuntu.com/daily-live/20120905.2/quantal-desktop-armhf+omap4.img on a Panda board.

@ Carla Sella

There is no need to continue to test & reproduce this bug. The bug is confirmed and it is being worked on. Simply choose on the very top that this bug affects you, and you will be notified when it is fixed.

Please wait until the bug is marked as fixed released.

the updates that fix this bug have been deployed to the webservice used to provide this functionality.
I am pleased to announce this but is fix released. \0/