Bug 100686 - keyboard not configured in firstboot
Summary: keyboard not configured in firstboot
Alias: None
Product: Fedora
Classification: Fedora
Component: rhgb   
(Show other bugs)
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
: 101220 105659 107187 107209 107219 107232 107277 121931 121951 122302 123940 133952 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-24 12:22 UTC by Féliciano Matias
Modified: 2007-11-30 22:10 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-30 16:56:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Féliciano Matias 2003-07-24 12:22:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
The keyboard is not configured in firstboot.

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

How reproducible:

Steps to Reproduce:
1. Do a fresh install of RedHat Linux and select an azerty keyboard for example.

Actual Results:  Querty keyboard in firstboot.

Expected Results:  keyboard configured as selected in anaconda.

Additional info:

Comment 1 Brent Fox 2003-07-24 14:33:31 UTC
Does the keyboard work at all or is it just the wrong keymap?

Comment 2 Féliciano Matias 2003-07-24 21:23:03 UTC
When i hit the 'a' key i see a 'q' char on the screen.
The keyboard work. It should be a wrong keymap.

Comment 3 Bill Nottingham 2003-07-28 20:34:24 UTC
If you boot with 'nogui', and firstboot is run *that* way, does it work?

Comment 4 Féliciano Matias 2003-07-28 23:41:04 UTC
Fresh installation of severn. Append "nogui" to grub with anaconda installer. At
the first boot, firstboot program is launched and there is no keyboard problem.

Comment 5 Bill Nottingham 2003-07-29 01:13:38 UTC
I expected as much. When rhgb is running, firstboot inherits rhgb's X server;
howerver, XKB doesn't work right with rhgb's X server, due to the read-only file
system, or somesuch.

Comment 6 Brent Fox 2003-07-29 13:36:03 UTC
Changing component to rhgb.

Comment 7 Bill Nottingham 2003-07-30 13:59:17 UTC
*** Bug 101220 has been marked as a duplicate of this bug. ***

Comment 8 Bill Nottingham 2003-09-26 19:53:56 UTC
*** Bug 105659 has been marked as a duplicate of this bug. ***

Comment 9 Brent Fox 2003-10-15 18:37:34 UTC
*** Bug 107187 has been marked as a duplicate of this bug. ***

Comment 10 Brent Fox 2003-10-15 22:57:17 UTC
*** Bug 107219 has been marked as a duplicate of this bug. ***

Comment 11 Brent Fox 2003-10-15 22:58:01 UTC
*** Bug 107209 has been marked as a duplicate of this bug. ***

Comment 12 Brent Fox 2003-10-16 00:40:01 UTC
*** Bug 107232 has been marked as a duplicate of this bug. ***

Comment 13 Christian Rose 2003-10-16 01:05:09 UTC
Also happens with Fedora Core test 3.

Comment 14 Brent Fox 2003-10-16 15:53:04 UTC
*** Bug 107277 has been marked as a duplicate of this bug. ***

Comment 15 Jonathan Blandford 2003-10-16 17:04:25 UTC
I have a tentative fix for this.  Can people try:

Comment 16 Jonathan Blandford 2003-10-16 21:30:21 UTC
scratch that.  That's not going to work quite correctly.  I'll get another test

Comment 17 Jonathan Blandford 2003-10-20 21:30:52 UTC
I am pretty sure I have this fixed in the latest rhgb/initscripts.

Comment 18 Douglas Peale 2004-05-02 21:33:48 UTC
*** Bug 122302 has been marked as a duplicate of this bug. ***

Comment 19 Féliciano Matias 2004-05-03 11:40:56 UTC
Reopen the bug.
appear again in FC2T3.

Comment 20 Luc Saillard 2004-05-10 08:55:31 UTC
I've the same problem with an azerty keyboard. When you add some user  
to the system, the keyboard is in qwerty. version FC2 Test3. 

Comment 21 Christian Rose 2004-05-18 21:57:41 UTC
The problem also appears in FC2 final.

This bug is especially problematic on the Add User screen. Full names
with non-ASCII characters cannot be entered correctly, and passwords
set may turn out to be wrong.
Because of the latter problem, which may cause an user to essentially
lock himself or herself out of the system, since the password set
won't be accepted later, I'm raising the severity to High.

Comment 22 marc frei 2004-05-24 00:56:30 UTC
I guess this bug give me the following behaviour (FC2 final with rhgb) :

I can't log within GDM if my user password is for instance "qwerty"
and the keyboard is supposed/known to be an "azerty" one....

In fact, you don't see what you type (*****) and I tested my keyboard
in the user/login field and this shown me that the keyboard is NOT the
"azerty" one before Gnome is fully started.

Once logged (after converting the passwords....), the "azerty"
keyboard is used : OK

So, this is definitivly "High" for users outside US.

Comment 23 Brent Fox 2004-05-24 18:59:00 UTC
*** Bug 121931 has been marked as a duplicate of this bug. ***

Comment 24 Brent Fox 2004-05-24 18:59:12 UTC
*** Bug 123940 has been marked as a duplicate of this bug. ***

Comment 25 Bernd Bartmann 2004-07-14 10:54:03 UTC
The bug still exists in FC3 Test1.

Comment 26 Daniel Veillard 2004-09-09 14:37:28 UTC
Okay, confirmed, reproduced ...
I knew I shouldn't have trashed my last azerty keyboard a few years
ago :-\


Comment 27 Daniel Veillard 2004-09-11 21:21:26 UTC
As Bill rightly guessed in #5 the keyboard bindings set in the
X11 configuration file won't work because the keymap is generated 
at stratup and with a read-only file-system well it just doesn't
work. I implemented a workaround which resets the X11 keymap
dynamically when firstboot is about to be run, and it seems to work :-)



Comment 28 Daniel Veillard 2004-09-13 16:37:22 UTC
*** Bug 121951 has been marked as a duplicate of this bug. ***

Comment 29 Daniel Veillard 2004-09-13 16:38:43 UTC
Version 0.12.6 was pushed on Rawhide and should fix this bug,


Comment 30 Daniel Veillard 2004-09-28 17:48:59 UTC
*** Bug 133952 has been marked as a duplicate of this bug. ***

Comment 31 David Balažic 2004-11-15 13:14:00 UTC
Fedora Core 3 has rhgb-0.14.1-1.i386.rpm and the bug is still there.

( I selected Slovenian layout in anaconda, but firstboot used US ( or
similar ) )


Comment 32 David Balažic 2004-11-15 13:15:19 UTC
... and adding myself to CC ( sorry for spam )

Comment 33 Daniel Veillard 2004-11-15 13:23:23 UTC
it works for other languages. What do you have in
/etc/sysconfig/keyboard ?
Also provide the subsection of your /etc/X11/xorg.conf
defining the keyboard.
This mean the lookup for *both* methods of Slovenian layout failed !


Comment 34 David Balažic 2004-11-15 13:30:26 UTC
I can't do that before tomorrow.

If it helps : At install I selected english install language,
Slovenian keyboard layout ( worked at once both in X and textual
console ) and some laguages for install ( english , Slovenian ,
Croatian, Hungarian and some more ).

After install in X the keyboard is Slovenian ( works OK ).

Comment 35 David Balažic 2004-11-16 06:43:41 UTC
cat /etc/sysconfig/keyboard



/etc/X11/xorg.conf :

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "si"

Comment 36 Daniel Veillard 2004-11-16 09:24:44 UTC
How is rhgb supposed to understand that "slovene" means "si" ?
That's why it broke, for a french configured keyboard you get
something based on the ISO country name like "fr" or "fr_FR".
I think the generation of the KEYTABLE value is wrong, potentially
an anaconda bug... Can you reopen a new bug pointing to this,
addressing anaconda, with me in CarbonCopy ? I don't feel reassigning
this big bug history and list is the right way to handle that specific



Comment 37 David Balažic 2005-04-21 12:22:22 UTC
I opened bug 155554 , Daniel.

Comment 38 John Thacker 2006-10-29 20:40:13 UTC
So, I see that the associated bug 155554 is closed rawhide.  Is this bug fixed,

Comment 39 Féliciano Matias 2006-10-30 04:41:02 UTC
(In reply to comment #38)
> So, I see that the associated bug 155554 is closed rawhide.  Is this bug fixed,
> then?

Yes for me.

Comment 40 Bill Nottingham 2006-10-30 16:56:55 UTC
Thanks, closing

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