Description of problem: The keyboard connected to the machine does not get configured before firstboot is run for the first time after Anaconda. While most of firstboot is point-and-click, there are some places were text input fields exist. Depending on the keyboard, inputing some values will be tricky (or maybe even impossible) because the keycodes are not mapped to the right values. How reproducible: Always Steps to Reproduce: 1. Use a keyboard where the equals sign is not in the same place as a US101 keyboard (i.e. a JP106) 2. Attempt to config LDAP authentication in firstboot right after an install 3. type in a DN that requires the use of the equals key (ex. "dc=redhat,dc=com") Actual results: when using a JP106, the equals signs will appear as underscores Expected results: the keymap configured in anaconda should be configured prior to firstboot running
*** This bug has been marked as a duplicate of 100686 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.