Bug 123542

Summary: keyboard setting from anaconda not used in firstboot (with be-latin1)
Product: [Fedora] Fedora Reporter: david paeme <david.paeme>
Component: firstbootAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: noarch   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:03:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description david paeme 2004-05-19 08:22:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040211 Firefox/0.8

Description of problem:
When be-latin1 is selected in anaconda during install, firstboot still
uses the standard US-keyboard setting. (i don't know if this error
exists for other keymaps too)

This can annoy users when trying to enter a user (different keymaps
make for difficult password typing.

English/US was selected as the only installed language.


This bug doesn't affect anything else else than firstboot

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

How reproducible:
Always

Steps to Reproduce:
1. start fedora installation
2. select be-latin1 (maybe others too?) as keymap on the second screen
3. continue installation with anaconda (keymap is ok here)
4. when firstboot runs, the keymap is wrong
    

Actual Results:  the keymap is wrong in firstboot, but when you
continue (booted to gdm for example), the keymap is ok (=the one
selected at the beginning of the installation).

Expected Results:  the selected keymap should be used in firstboot

Additional info:

Comment 1 Alan Cox 2004-05-22 00:23:33 UTC

*** This bug has been marked as a duplicate of 121931 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:17 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.