Marking as fixed, given the comments confirming it being resolved in the
final release. If you are still experiencing this issue in Karmic,
please file a new bug or feel free to reopen this one.
Thanks!
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Fix Released
--
Installer
I do believe this was fixed before release. Can anyone still confirm it
on Ubuntu or Kubuntu?
** Changed in: ubiquity (Ubuntu)
Status: New = Incomplete
--
Installer highlights incorrect time zone for some cities
https://bugs.launchpad.net/bugs/341375
You received this bug notification
Not sure about Johannesburg, but most other cities are now correct in
Ubuntu.
Dmitriy
Dmitriy Plaks
dmitriy...@gmail.com
On Tue, Jul 7, 2009 at 8:58 AM, Evan Dandrea ev...@ubuntu.com wrote:
I do believe this was fixed before release. Can anyone still confirm it
on Ubuntu or Kubuntu?
**
** Description changed:
Jaunty daily, 2009-03-11
Jaunty alpha 6
1. In the installer, advance to the Where are you? step.
2. From the menus, choose any of these cities:
- America New York
- America Los Angeles
- Australia Perth
- Australia Melbourne
-
It's not fixed for Zurich yet in the Kubuntu Beta. See attached .png.
The time displayed is correct. It's just that the wrong timezone is
highlighted.
** Attachment added: Zurich in the wrong timezone
http://launchpadlibrarian.net/25329035/timezone.png
--
Installer highlights incorrect time
This seems to be fixed in Beta
--
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
ubuntu-bugs@lists.ubuntu.com
** Summary changed:
- Incorrect timezone shown in graphical map
+ Installer highlights incorrect time zone for some cities
** Description changed:
- In 9.04 daily from 3/11/09
+ Jaunty daily, 2009-03-11
+ Jaunty alpha 6
- What happens:
- When using the new timezone map to select my timezone,
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
