RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1025354 - wrong timezone for Czech
Summary: wrong timezone for Czech
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 14:25 UTC by Karel Volný
Modified: 2013-11-01 17:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-01 10:15:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Karel Volný 2013-10-31 14:25:02 UTC 
Description of problem:
I've tried to install RHEL7 in Czech, but I got Europe/London time zone preselected. It should be Europe/Prague.

Version-Release number of selected component (if applicable):
latest nightly

How reproducible:
always

Steps to Reproduce:
1. run the installer
2. on the language screen, choose Czech
3. on the next screen, look at date time settings

Actual results:
the time zone is Europe/London

Expected results:
the time zone should be Europe/Prague

Additional info:
of course there are some Czech speaking people located in London, but I guess Czech Republic (=> Prague) is the home of vast majority of Czech users :-)
Comment 1 David Shea 2013-10-31 14:32:59 UTC 
The default timezone is based on a GeoIP lookup, not language selection. Do you think the geoip data is in error? Can you post the logs from /tmp?
Comment 4 Karel Volný 2013-11-01 14:46:45 UTC 
hm, I wonder whether using unrelieable geoip is better choice than also unrealiable bond between language and territory (but at least set by user and not by machine), but I guess this horse is dead already ...
Comment 5 Martin Kolman 2013-11-01 17:23:42 UTC 
(In reply to Karel Volný from comment #4)
> hm, I wonder whether using unrelieable geoip is better choice than also
> unrealiable bond between language and territory (but at least set by user
> and not by machine), but I guess this horse is dead already ...
Well, it just preselects the language and the users still has to confirm it. Also it is disabled for automated installs.

Regarding timezones, the territory<->timezone (or actually area/city<->timezone, so that countries like Canada or Russia get correct timezones) works much better.

BTW, regarding the territory<->language mapping, this is handled by the langtable project, which is maintaining (among others) weighted tables of territory<->language mappings. So if GeoIP detects you are in the UK, it gives you English first, followed by the other local languages, like Welsh and Gaelic (but as Anaconda has a translation in only on of them, only language other than English is shown for the UK).

So if you find and weird territory<->language mappings or similar l10n issues, this are valid bugs that should be reported against langtable, so that they can be fixed.
Note You need to log in before you can comment on or make changes to this bug.