I believe this is tied to Daylight Savings Time. If the date is set to early February (standard time), most of these problems go away. In the US, most cities get the timezone offset with a test date of June 2, 2009.
Perhaps a good solution to this (if the installer can differentiate between standard and daylight savings time) is to only use standard time. Not sure how hard it would be to patch though. Here's a list of a few problem cities (Tested with date set to Feb 2, 2009): Americas: Argentina/ Buenos Aires Argentina/ Coboda Argentina/ Jujuy Argentina/ Tucuman Caracas (no timezone highlighted) Montevideo Sao Paulo Australia: Adelaide (no timezone highlighted) Broken Hill (no timezone highlighted) Currie Eucla (no timezone highlighted) Hobart Melbourne Perth Sydney Asia: Colombo (no timezone highlighted) Kolkata (no timezone highlighted) Antarctica: Davis Mawson McMurdo (no city shown) South Pole (no city shown) Vostok (no city shown) Indian: Mauritius Pacific: Apia (no city shown) Auckland Chatham (no timezone highlighted, no city shown) Easter Enderbury Kiritimati (no timezone highlighted) Midway (no city shown) Walllis -- Installer highlights incorrect time zone for some cities https://bugs.launchpad.net/bugs/341375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
