From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 Description of problem: The ] key is ignored by X11 when the keyboard set up is configured for model abnt2 layout br. The problem is that, in /usr/X11R6/lib/X11/xkb/geometry/pc, xkb_geometry "abnt2" mentions both <AC12> and <BKSL>, in their correct positions, but /etc/X11R6/lib/X11/xkb/keycodes/pc aliases AC12 to BKSL in xkb_keycodes "basic", and then xkb_keycodes "abnt2" sets <BKSL> to 94, without setting <AC12> to 51, that is the correct value for the `]' key. I don't understand why 51 is right, given that the scan code of the key is 0x2b, but still, it works. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Get a br abnt2 keyboard. 2.Configure for a br abnt2 keyboard 3.Type the `]' key. Actual Results: It does nothing. Expected Results: A `]' should be generated. Additional info: Fix: in /usr/X11R6/lib/X11/xkb/keycodes/pc, add to the xkb_keycodes "abnt2" section the following line: <AC12> = 51; then restart X or get it to re-read the keyboard configuration.
Oops, where I wrote .../keycodes/pc, I meant .../keycodes/xfree86, sorry. BTW, apologies for not having caught this one in the beta :-(
I've added the proposed fix to XFree86-4.1.0-5, which should be available shortly for testing.
This file is now very weird, and I am sure it is broken, but have no idea what is correct. It currently shows: // Keys that are generated on Japanese and Brazillian keyboards alias <AC12> = <BKSL>; ... ... // For brazilian ABNT2 keyboard. by Ricardo Y. Igarashi(iga.br) xkb_keycodes "abnt2" { include "xfree86(basic)" <AC12> = 51; <BKSL> = 94; <AC12> = 51; }; That is almost certainly incorrect. I'm removing the patch for now which will disappear in build 4.2.0-6.41. Please let me know if this breaks support, and we will try to find the correct fix.
The alias was already there back when I wrote the patch, but it was not appropriate for abnt2, which is why both AC12 and BKSL were introduced. Of course, the duplicate definition of AC12 in the abnt2 section is not necessary. Perhaps you installed my suggested fix, then the duplicate came in in a merge from XFree86, since my patch made it to the XFree86 CVS tree as of 4.2.0?
Unfortunately, on Red Hat Linux 7.3, the ]} key produces \|, whereas the \| key produces <>. Ouch! I'm looking into fixing this. (would it have been better to open a new bug report, so that queries on 7.3 would find this?)
Hmm... Could it be that the order of the entries matter, given that AC12 is defined as an alias to BKSL earlier in the file? This used to work in 7.2: xkb_keycodes "abnt2" { include "xfree86(basic)" <AC12> = 51; <BKSL> = 94; }; but this is what came with 7.3: xkb_keycodes "abnt2" { include "xfree86(basic)" <BKSL> = 94; <AC12> = 51; }; Unfortunately, I don't have easy access to abnt2 keyboards. I should probably buy one just to be able to test stuff like this. It's a shame that, for every release, I say the earlier problems were fixed, but new ones manage to creep in, and they go unnoticed until I install non-betas at the uni, where such keyboards are common. :-( Anyway, I'll ask people at the uni to give it a try and report back.
unfortunately, changing the order of the keys didn't help. I'm now at a loss of what to try :-( Suggestions?
Found it. The problem was that anaconda was generating the kbd configuration with XkbModel "pc102", instead of "abnt2" that would have made it work.
I've no idea what the proper solution to this problem is. Please contact XFree86.org directly, as that is the speediest way to a proper solution. Closing bug WONTFIX.
*** This bug has been marked as a duplicate of 70351 ***