Bug 145627 - Can't input english if indic/russian keyboard is selected during installation
Can't input english if indic/russian keyboard is selected during installation
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: firstboot (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Max Spevack
: i18n
Depends On:
Blocks: Indic 155574 156322 157870 Russian
  Show dependency treegraph
 
Reported: 2005-01-20 01:25 EST by Jatin Nansi
Modified: 2007-11-30 17:07 EST (History)
5 users (show)

See Also:
Fixed In Version: RHBA-2005-711
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-05 13:13:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jatin Nansi 2005-01-20 01:25:56 EST
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:
Comment 1 Leon Ho 2005-02-07 10:51:29 EST
That maybe need to fix on anaconda end to provide switching of the key
layout?
Comment 2 Jens Petersen 2005-03-18 04:00:13 EST
Any news on this?
Comment 3 Jens Petersen 2005-05-16 10:44:11 EDT
Is this still reproducible with RHEL4?
Comment 4 Jens Petersen 2005-05-16 11:52:54 EDT
Aalam tells me this is apparently only reproducible from a cdrom install
(or with "linux nopass"), and it is still happening with fc4test3.
Comment 6 Debbie McGrath 2005-06-08 14:02:36 EDT
This bug is considered CanFix for RHEL 4 U2 by RHN Engineering.
Comment 8 Lawrence Lim 2005-06-16 03:59:10 EDT
I have experience the same problem when installing with Russian keyboard during
anaconda install.
Comment 11 Debbie McGrath 2005-06-22 09:53:34 EDT
Devel & PM ACK for U2
Comment 13 Adrian Likins 2005-07-29 13:00:29 EDT
What is "the right thing" and the approriate places, and what does firstboot
need to do to take this into account?
Comment 14 Jens Petersen 2005-07-31 02:40:42 EDT
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.
Comment 15 Leon Ho 2005-08-01 01:01:49 EDT
Yup, Jens' suggestion is good. Is it possible to enforce to use ascii input in
firstboot's X environment?
Comment 17 Adrian Likins 2005-08-01 14:58:02 EDT
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.
Comment 18 Adrian Likins 2005-08-08 12:02:41 EDT
firstboot-1.3.39-4
Comment 20 Max Spevack 2005-09-06 15:13:36 EDT
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
Comment 21 Todd Warner 2005-09-23 17:47:21 EDT
PROD_READY is a deprecated state. This bug is now RELEASE_PENDING.
Comment 22 Red Hat Bugzilla 2005-10-05 13:11:17 EDT
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
Comment 23 Red Hat Bugzilla 2005-10-05 13:13:12 EDT
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

Note You need to log in before you can comment on or make changes to this bug.