Hide Forgot
Description of problem: If user selects an indic keyboard layout as default during the install, its not possible to input any english during firstboot. Its possible to input english during the install and after bootup, the problem is only during firstboot. Tested on RHEL4-RC-0107.0 WS Version-Release number of selected component (if applicable): 1.3.39-2 How reproducible: Everytime Steps to Reproduce: 1. Select an indic keyboard during installation 2. Complete install and reboot into firstboot 3. Actual results: Cannot input any english text in firstboot Expected results: Should be able to input english Additional info:
That maybe need to fix on anaconda end to provide switching of the key layout?
Any news on this?
Is this still reproducible with RHEL4?
Aalam tells me this is apparently only reproducible from a cdrom install (or with "linux nopass"), and it is still happening with fc4test3.
This bug is considered CanFix for RHEL 4 U2 by RHN Engineering.
I have experience the same problem when installing with Russian keyboard during anaconda install.
Devel & PM ACK for U2
What is "the right thing" and the approriate places, and what does firstboot need to do to take this into account?
Simple answer is I don't know... it is strange that this only affects firstboot though: are there any differences wrt to X configuration for firstboot from anaconda/normal X sessions? Specially wrt to kbd setup? Anyway firstboot should just allow ascii input with any keyboard.
Yup, Jens' suggestion is good. Is it possible to enforce to use ascii input in firstboot's X environment?
Trying to use rhpl.keyboard to setup/activate the right keymap if we start up X ourself. I'm guessing that might be it, testing now.
firstboot-1.3.39-4
Tested that package via firstboot --reconfig and chose "Russian" and also "Russian (cp1251)" as the keyboard types. Was still able to enter text during the rest of firstboot. PROD_READY
PROD_READY is a deprecated state. This bug is now RELEASE_PENDING.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-713.html
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-711.html