Red Hat Bugzilla – Bug 473226
picking estonian (et-ee) keyboard layout at install gives you ethiopian keyboard at first login
Last modified: 2009-12-18 01:58:18 EST
Description of problem: Linux newbies in estonia are returned to windows devotees because picking estonian keyboard at install time the system denies users access because of the characters typed in the gdm login screen are ethiopian and thus do not match the password created whilst installed. Even the keyboard layout chooser does not help much.
Version-Release number of selected component (if applicable):
install Core 10 and specify estonian keyboard during the install process. You will hit the bug during the first login with 100% certainty.
Steps to Reproduce:
1. Select estonian keyboard during the install
2. observe the ethiopian keyboard layout presented during the first login
the system has switched from estonian keyboard layout to ethiopian.
no keyboard layout switching should occur.
it has probably something to do with mixup concerning keyboard layout abbreviations and TLD extensions with .et being ethiopian top level domain
I can confirm this behavior as being "always" reproducible. The symptoms point to gdm, not anaconda, since firstboot accepts the name and password for the non-root user correctly.
Regarding this bug's priority: Selecting the Estonian keyboard before entering the password is an easy work-around, but it might be confusing to novices.
Is there a file I can change the keyboard setting in? Because of bug 442533, my login screen is black - I am unable to see what I am doing during login and I am unable to correct my keyboard setting. I would like to be able to login blind, so I can do further testing for bug 442533.
sounds like an anaconda issue. If selecting estonian works, then gdm is getting it right.
Can you attach
Created attachment 326810 [details]
Created attachment 326811 [details]
Ray - does gdm look at the KEYTABLE= setting in /etc/sysconfig/keyboard?
Oh, Jeremy explained that he made some changes to rhpl that should fix this, though there's some confusion as to what release they ended up in. Reassigning to him as a reminder.
No, it gets its layout information from libxklavier which gets it from xkeyboard-config
I believe that we just use the X default config if the user hasn't picked anything different.
It looks like X uses /usr/bin/fedora-setup-keyboard to pull from /etc/sysconfig/keyboard
Maybe it should be doing
eval `rhplquery $LAYOUT`
eval `rhplquery $KEYTABLE`
(I wrote comment 8 before reading comment 7)
fedora-setup-keyboard is in the X package. --> ajax
*** Bug 476615 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.