From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 Description of problem: When br-abnt2 is selected as the keyboard at install time, anaconda generates XF86Config with XkbModel "pc102", instead of "abnt2". This causes at least two keys not to function properly. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Choose Brazilian (br-abnt2) keyboard at install time 2.After installation, try to type ], }, \ or | in the X login screen. Actual Results: You get \, |, < and >, respectively. Oops. Expected Results: Just what I typed in :-) Additional info:
*** Bug 55128 has been marked as a duplicate of this bug. ***
I failed to mention that this problem affects only XFree86, not text mode, which is why I thought it was an anaconda problem, not a redhat-config-keyboard one. Jeremy has clarified that redhat-config-keyboard holds the config data, even though it doesn't set up XF86Config itself.
Should be fixed in redhat-config-keyboard-0.9.7-2. Anaconda has it's own way of writing out the initial XF86Config file, but redhat-config-keyboards can now change the values in XF86Config after install. If anaconda is writing out the wrong values, please open a new bug against it. QA, please verify.
Still having issues with this one. The bug is actually in rhpl, so changing component and attaching diff.
Created attachment 69524 [details] Diff to fix abnt2 mapping
Ah, the original bug was that redhat-config-keyboard wasn't modifying XF86Config. So I fixed that, only to find out that rhpl's keyboard list was incorrect. Will fix now.
Should be fixed in rhpl 0.34-1. Thanks for the patch, Jay.
Fix confirmed in rhpl-0.39-1.