xorg-x11-18.104.22.1683-1 (as built by Mike Harris for Fedora Core development) has
a major regression in the br-abnt2 keyboard description. The key used to input
slash and question mark has no effect. According to Red Hat bugzilla 130789,
removing the `<AB11> = 123;' line from the abnt2 definition in
xkb/keycodes/xfree86, the problem goes away. I can't quite figure out why this
line is there. It wasn't in the previous release of xorg-x11. Could it please
be taken out? Thanks,
Marking as a blocker for 6.8.0, as suggested by Mike Harris.
was introduced with #533
We had reports with Cygwin/X that this key does not work.
Which keycode is associated to that key?
I'll try to find that out, but 123 is assigned to both AB11 (in abnt2) and to
KPDC (inherited from xfree86(basic)). This can't be right, can it?
My abnt2 keyboard works fine with Fedora's xorg-x11-6.7.0-5. The abnt2
description in xkb/keycodes/xfree86 doesn't define a keycode value for <AB11>,
but basic defines it as 211.
I'd asked Ulisses to look for a key with code 123, and he couldn't find any such
key. He confirms FC2's xorg-x11 works perfectly with an ABNT2 keyboard. Clovis
(from the Red Hat bugzilla bug report) confirms xorg-x11 in rawhide (pre-6.8.0)
fails, and that reverting the change gets the keyboard back to a functional state.
Windows reports keycode 123 for that key. Old XFree reported it too. I found
references all over the net which use 123 for this key.
Why was it changed?
The same problem is pending for two keys on the jp106 keyboard
Created attachment 803 [details] [review]
We talked about this bug on the call today, and thought that the fix looked okay
for this release. We should look at fixing up other keycode related issues
after this release.
Patch is checked in. Moving to bug 999 for documentation in the release notes.
Closing bug as "FIXED" from Kevin's comment above.
Keep the bug open. It must be investigated after the release.
I'll ship the cygwin build with <AB11> = 123 to avoid a regression on cygwin but
this must be solved after the release.
I've adjusted the keycodes for the two keys in XWin. This should fix the problem
for cygwin and will not affect other systems again.
marking as FIXED