[evdev] ABNT2 missing keys

[Hebert]

Binary package hint: xserver-xorg-core

after latest update on intrepid, some keys on my keyboard (ABNT2, Brazilian Portuguese) stop working.

Some multimedia keys (play.pause, stop.. ) and the (? / «) key also stop working.

On the Gnome-Keyboard preferences, my keyboard is being recognized as Evdev-managed Keyboard

When I manually change to ABNT2 Brazilian, several others keys start to show the same issue.

xserver-xorg-core:
  Instalado: 2:1.4.99.906-1ubuntu2
  Candidato: 2:1.4.99.906-1ubuntu2
  Tabela de versão:
 *** 2:1.4.99.906-1ubuntu2 0
        500 http://br.archive.ubuntu.com intrepid/main Packages

xserver-xorg-input-evdev:
  Instalado: 1:2.0.3-2
  Candidato: 1:2.0.3-2
  Tabela de versão:
 *** 1:2.0.3-2 0
        500 http://br.archive.ubuntu.com intrepid/main Packages

Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid

[Timo Aaltonen (tjaalton)]

Don't do that, the model should always be evdev since when evdev driver is used.

Do the keys produce events? You can test that with xev. What keys are not working?

The multimedia key shortcut defaults need to be changed in gnome-control-center.. they probably

[Hebert (hebert-bernardo)]

The Multimedia keys seems to have some kind of response of xev:

KeyPress event, serial 34, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1270921, (113,678), root:(1630,729),
    state 0x10, keycode 171 (keysym 0x1008ff17, XF86AudioNext), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1271041, (113,678), root:(1630,729),
    state 0x10, keycode 171 (keysym 0x1008ff17, XF86AudioNext), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1277970, (113,678), root:(1630,729),
    state 0x10, keycode 173 (keysym 0x1008ff16, XF86AudioPrev), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1278026, (113,678), root:(1630,729),
    state 0x10, keycode 173 (keysym 0x1008ff16, XF86AudioPrev), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 36, synthetic NO, window 0x4800001,
    mode NotifyNormal, detail NotifyNonlinear

_ _ _ _ _ _ _ _ _

But the keyboard key ( ? / ) stop working:

KeyPress event, serial 34, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1182541, (161,595), root:(1678,646),
    state 0x10, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1182629, (161,595), root:(1678,646),
    state 0x10, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

ConfigureNotify event, serial 34, synthetic NO, window 0x4800001,
    event 0x4800001, window 0x4800001, (1515,49), width 178, height 178,
    border_width 2, above 0x4400041, override NO

ConfigureNotify event, serial 34, synthetic YES, window 0x4800001,
    event 0x4800001, window 0x4800001, (1515,49), width 178, height 178,
    border_width 2, above 0xe00301, override NO

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

There is no output In comparision with the working letter ( a ) key below:

KeyPress event, serial 31, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1139995, (104,485), root:(1621,536),
    state 0x10, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XmbLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1140075, (104,485), root:(1621,536),
    state 0x10, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

_ _ _ _ _ _

It got messed up after the latest release

Hope that helps.

[Hebert (hebert-bernardo)]

Just to clear things out, I am already using de evdev driver.

Another thing I noticed is the keyboard time response "repeat" became to fast.

[Olivier (olivier-lacroix)]

I suspect this bug to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/255008

Please confirm that it is or is not

[Hebert (hebert-bernardo)]

No exactly.

Only if I change my keyboard to Brazilan ABNT inside Gnome-keyboard manager, the upper arrow starts to take screenshots.

But, only if I change settings.

My problem is the ( ? / ) key went dead.

My multimedia keys stop working either. But, like I posted above, they are "alive". At least for xev, so, it must be a configuration problem "tunning" in the future will do the job.

I just noticed another thing, on the numpad the ( . ) key is not working properly, it shows a ( , ) for now.

Hope that helps.

[Timo Aaltonen (tjaalton)]

Please attach the output of 'setxkbmap -print'

[Hebert (hebert-bernardo)]

Here it is

$ setxkbmap -print

xkb_keymap {
 xkb_keycodes { include "evdev+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+br+inet(evdev)" };
 xkb_geometry { include "pc(pc104)" };
};

[Timo Aaltonen (tjaalton)]

Could you try changing the layout to "us", and see if it changes anything in the behaviour.

[Hebert (hebert-bernardo)]

I just did that.

$ setxkbmap -print

xkb_keymap {
 xkb_keycodes { include "evdev+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+br+inet(evdev)+us:2+level3(ralt_switch_for_alts_toggle):1+level3(ralt_switch_for_alts_toggle):2+group(alts_toggle)" };
 xkb_geometry { include "pc(pc104)" };
};

Nothing has changed.

It's strange. It shouldn't be showing these characters:

 "ç" "á" "à" "ü"

the "( ? / )" key is still dead.

xev's output:

KeyPress event, serial 34, synthetic NO, window 0x3e00001,
    root 0x82, subw 0x0, time 40473547, (933,155), root:(940,206),
    state 0x2010, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3e00001,
    root 0x82, subw 0x0, time 40473571, (933,155), root:(940,206),
    state 0x2010, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Thanks for reading.

[Daniel Luz (mernen)]

I am having the exact same problem.

The "/ ?" stopped working once I upgraded to Intrepid, and xev emits the same output as it does for Herbert.

As for the multimedia keys, I just reconfigured the shortcuts via gnome-keybinding-properties, and they all seem to work. Thanks.

[Iñaki García Etxebarria (inaki-garetxe)]

Same problem here with a japanese keyboard (pc106).

The symbols that do not work and used to work before the latest upgrades (that caused also bug #255008) are ']' and '}' (which in the japanese keyboard are in the same key), and the key for '\' and '_' (underscore, one key again).

It still works fine in the console, and it used to work fine in hardy with the appropriate xorg.conf. (The yen key has always been kind of borken too, but that's a different bug, and not a regression like this).

 Option "XkbRules" "xorg"
 Option "XkbModel" "jp106"
 Option "XkbLayout" "jp,jp"
 Option "XkbVariant" "106,"
 Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"

A simple way to see that something is broken (some keys are missing) is when I try to add a japanese layout, attached goes a screenshot of that.

Notice that there is no key for ']', '}', which in the japanese keyboard are on the same key (you use shift to select '}'), and take half of the space assigned to 'Return' in the attached layout. Similarly for '\', '_', this key should be taking half of the space assigned to 'Shift_R'.

[Timo Aaltonen (tjaalton)]

Forwarded from https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/255372

The ( ? / ) key stops working after input-hotplug was applied, ie. the evdev driver and model.

The key produces this in xev:

KeyPress event, serial 34, synthetic NO, window 0x4800001,
    root 0x82, subw 0x0, time 1182541, (161,595), root:(1678,646),
    state 0x10, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

$ setxkbmap -print

xkb_keymap {
 xkb_keycodes { include "evdev+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+br+inet(evdev)" };
 xkb_geometry { include "pc(pc104)" };
};

[Timo Aaltonen (tjaalton)]

so, this much we managed to debug this on our own:

symbols/br(abnt2) defines AB11 as [ slash, question, degree,
 questiondown ]
symbols/inet(evdev) redefines AB11 as XF86Launch4.

not only that, but the keycodes seem to be mixed up. 97 has RO..

[Sergey V. Udaltsov (svu)]

This bug is distro-specific. Ubuntu applied the patch which uses model evdev regardless of the actually chosen model. You should use abnt2 model - and ask Ubuntu not to use evdev unless it is really needed.

[Timo Aaltonen (tjaalton)]

with the evdev driver there is no other working model than evdev, otherwise you have all sorts of funky effects when keys are wrongly mapped, see launchpad bug 255008. You maybe didn't know that Fedora does the same now.

[Sergey V. Udaltsov (svu)]

Yes I know about fedora. And I am not terribly happy with that. What I can propose (for linuxes only - dirty hack!) is
1. Optional. Adding abnt2 section to keycodes/evdev - with missing keycodes. I am not sure what is the status of the keycode KPPT in evdev.
2. patching rules/base in order to use evdev keycodes wherever possible. The section would look like:
! model = keycodes
  amiga = amiga(de)
  ataritt = ataritt(de)
  sun4 = sun(type4_euro)
  sun5 = sun(type5_euro)
  sun6 = sun(type6_usb)
  pc98 = xfree98(pc98)
  abnt2 = evdev(abnt2)
(previous line is optional, if no abnt2 section is needed)
  jp106 = xfree86(jp106)
  evdev = evdev
  olpc = evdev
  macintosh_hhk = macintosh(hhk)
  macintosh_old = macintosh(old)
 $macbooks = macintosh+macintosh(goodmap)
 $macs = macintosh
  thinkpadz60 = xfree86(thinkpadz60)
  * = evdev

In that case, the patch in ubuntu/fedora should be reverted. And people should choose abnt2, not evdev.

To make a proper fix, I have to think about that problem some more time...

[Timo Aaltonen (tjaalton)]

Iñaki: could you open a new bug please? This bug is about ABNT2. Also, attach the output of 'xkbcomp :0 -' and 'setxkbmap -print', thanks.

[Daniel Stone (daniels)]

On Fri, Aug 15, 2008 at 05:35:15PM -0700, <email address hidden> wrote:
> --- Comment #4 from Sergey V. Udaltsov <email address hidden> 2008-08-15 17:35:14 PST ---
> Yes I know about fedora. And I am not terribly happy with that. What I can
> propose (for linuxes only - dirty hack!) is
> 1. Optional. Adding abnt2 section to keycodes/evdev - with missing keycodes. I
> am not sure what is the status of the keycode KPPT in evdev.
> 2. patching rules/base in order to use evdev keycodes wherever possible. The
> section would look like:

This is why I was suggesting different rules. Even with evdev, you
still have some variance between models, and your options are
essentially to have your models as evdev, evdev_abnt2, etc, or to create
a new ruleset called evdev, and let the model field actually refer to
models again.

evdev is here to stay, so we're going to have to deal with it somehow.

[Sergey V. Udaltsov (svu)]

Now, we have evdev ruleset - and xorg code is using it for the driver evdev. If abnt2 needs special keycodes for evdev - feel free to contribute to keycodes/evdev(abnt2) - for a moment it is dummy

[Iñaki García Etxebarria (inaki-garetxe)]

Sorry. I just opened bug #258595. Thanks!

[LucasLinard (lucaspglinard)]

My keyboard has the same problems. when I press the "( ? / )" nothing happens
everything else is fine now.
I'm using kubuntu so I don't know how the keyboard isconfigured under "Gnome-Keyboard preferences". At system settings > regional e language > keyboard layout, it says enable keyboard layouts. the command option is "setxkbmap -model evdev -layout br -variant "
lucas@lucas-desktop:~$ setxkbmap -print
xkb_keymap {
        xkb_keycodes { include "evdev+aliases(qwerty)" };
        xkb_types { include "complete" };
        xkb_compat { include "complete" };
        xkb_symbols { include "pc+br+inet(evdev)" };
        xkb_geometry { include "pc(pc104)" };
};
the xev output when i press "( ? / )" is:
KeyRelease event, serial 34, synthetic NO, window 0x1600001,
    root 0x1a6, subw 0x0, time 1198702, (115,671), root:(120,696),
    state 0x10, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
attached is a file with the output of "xkbcomp :0 -"

[Rodolfo Lima (rodolfo-rodsoft)]

While this is not a proper solution, this hack seems to work.
I had to modify 2 files:

/usr/share/X11/xkb/keycodes/evdev:

The line that reads: <AB11> = 211
should be changed to: <AB11> = 97
The line that reads: <AD01> = 97; // Romaji
should be commented out: // <AD01> = 97; // Romaji

and

/usr/share/X11/xkb/symbols:

The line that reads: key <AB11> { [ XF86Launch4 ] };
should be commented out: // key <AB11> { [ XF86Launch4 ] };

After doing those and restarting X, I'm able to use / ? °

[Timo Aaltonen (tjaalton)]

Things are progressing.. I'm about to upload a new xkeyboard-config and with that we can set the rules as evdev, and then add these exotic models inside the rules like they are in base currently. This also needs synchronized uploads of hal, gnome-settings-daemon and evdev, but slowly getting there..

[Bremm (bremm)]

Same issue here.

KeyRelease event, serial 34, synthetic NO, window 0x3600001,
    root 0x13b, subw 0x0, time 169384988, (51,-18), root:(802,445),
    state 0x0, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

$ setxkbmap -print
xkb_keymap {
 xkb_keycodes { include "evdev(abnt2)+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+br+inet(evdev)+level3(ralt_switch)" };
 xkb_geometry { include "pc(abnt2)" };

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "br,ru(phonetic)"
 Option "XkbOptions" "lv3:ralt_switch"
EndSection

Aside notes: I've been using ru_phonetic as 2nd layout and my kb has 111 keys (without multimedia).

Now going to test Rodolfo Lima's hack.

[Bremm (bremm)]

OK. phase 1 finished, since my /usr/share/X11/xkb/keycodes/evdev is slightly different.

In session "Keys that are generated on Japanese keyboards" I've did:

 <AB11> = 211; // backslash/underscore

changed to

 <AB11> = 97; // backslash/underscore

and
 <RO> = 97; // Romaji

commented out

 //<RO> = 97; // Romaji

Now "?" (shift + /) and "°" (ralt + /) work. Now going to fix "/" since only numpad key works.

[Rodolfo Lima (rodolfo-rodsoft)]

Sorry everyone, I've incorrectly transcribed my hack.
Bremm got the first part right.

The second deals exactly with "/". The file to be modified is
/usr/share/X11/xkb/symbols/inet. The modification itself is correct, that is:

The line that reads: key <AB11> { [ XF86Launch4 ] };
should be commented out: // key <AB11> { [ XF86Launch4 ] };

This will make "/" appear when the corresponding key is pressed.

[Bremm (bremm)]

I was about to deal with second part, but not sure about which file to edit. Anyway I'm here to confirm that Rodolfo Lima's procedure (2nd part) works as a charm.

Thanks!

[Gabriel Mazetto (brodock)]

just to let you know, i have the same problem with the slash and the question mark (also using an ABNT2 Keyboard - Brazilian)

this is the output for the Slash

KeyPress event, serial 31, synthetic NO, window 0x4400001,
    root 0x1a6, subw 0x0, time 158248712, (-67,108), root:(607,162),
    state 0x10, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4400001,
    root 0x1a6, subw 0x0, time 158248776, (-67,108), root:(607,162),
    state 0x10, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

and this is for the Question Mark (i have striped out the one for the Shift)

KeyRelease event, serial 34, synthetic NO, window 0x4400001,
    root 0x1a6, subw 0x0, time 158494800, (-195,327), root:(479,381),
    state 0x11, keycode 97 (keysym 0xff24, Romaji), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

[Timo Aaltonen (tjaalton)]

I don't think it's necessary to change symbols/inet, since if you use the ABNT2-model, you should also be using symbols/br (or symbols/jp if JP106), and AB11 is remapped there. I'm about to upload a new version which should fix this, so please test when xkb-data 1.3-2ubuntu3 is available. Thanks for the patience and letting us know what needed to be done!

[Launchpad Janitor (janitor)]

This bug was fixed in the package xkeyboard-config - 1.3-2ubuntu3

---------------
xkeyboard-config (1.3-2ubuntu3) intrepid; urgency=low

  * 100_abnt2_jp106.diff: Fix keycodes/evdev to better support ABNT2 and
    JP106. (LP: #255372, #258595)

 -- Timo Aaltonen <email address hidden> Tue, 16 Sep 2008 16:47:08 +0300

[pinduvoz (pinduvoz)]

I just install the package xkb-data 1.3-2ubuntu3 (the sama as xkeyboard-config - 1.3-2ubuntu3, I presume) and the bug still not fixed. Thre "?" now works, but the "/" don't.

Best regards,

Pinduvoz

[Timo Aaltonen (tjaalton)]

yeah, you are right, the symbols are loaded in this order:

pc -> br -> inet(evdev)

which means that AB11 is overridden in inet(evdev). Maybe changing AB11 to I211 would be the correct fix.

[Timo Aaltonen (tjaalton)]

-2ubuntu4 should fix this.

[Rodolfo Lima (rodolfo-rodsoft)]

Thanks for the fix. I won't be able to test it this week because my Intrepid box is at work (and I'm on vacation), and I use Gentoo at home (yes, it should be the other way around, but I like to live in danger),

[Bremm (bremm)]

2008/9/17 Rodolfo Lima <email address hidden>:
> Thanks for the fix. I won't be able to test it this week because my
> Intrepid box is at work (and I'm on vacation), and I use Gentoo at home
> (yes, it should be the other way around, but I like to live in danger),

LOL, Gentoo isn't that dangerous. I've just joined Ubuntu because I
want help in a easy-to-use distro for people as my mother, that barely
know how to hold a mouse and type on keyboard. :-)

BTW, -2ubuntu3 just arrived here. When -2ubuntu4 arrives, I'll restart
X to see if all is OK.

Have fun at your vacation and thanks for all support.
--
Márcio Bremm -- http://vtnc.org/

Pessoas não mudam, apenas mascaram sua real identidade.
People don't change, only mask their real identity.
Люди не меняются, только маскируют свою реальную идентичность.

[pinduvoz (pinduvoz)]

At the moment, after updating the system, all is working as it should be.

Thanks for the good work, guys.

Best regards,

Pinduvoz

[Timo Aaltonen (tjaalton)]

Great, thanks for testing.

[Hebert (hebert-bernardo)]

Hi,

I had to migrate to Debian SID and It is good to see this problem gone.

I just tested the very latest daily-live CD and it appears is really solved.

But, I also noticed that on the numpad the dot ( . ) key is actually printing a comma ( , )

Can anyone else using the ABNT2 keyboard confirm this odd behavior on a real installation or is contained to Daily-Live?

Thanks for the good work to all involved.

[Bremm (bremm)]

Here, with Xubuntu 8.10, it's comma placed on dot (xkb-data_1.3-2ubuntu4_all.deb). Since our decimal mark is comma, who has ABNT2 scheme should have it instead of dot. The exception belongs to countries that don't follow the metric system: USA, England, Ireland, Australia and others with imperial system.

[Daniel Luz (mernen)]

Yes, I can confirm the . and , keys are swapped. I hadn't reported that yet because I wanted to make sure it wasn't like that before, but I hadn't had the time yet.

These are the KeyPress events for the period and comma keys, respectively:

KeyPress event, serial 32, synthetic NO, window 0x4c00001,
    root 0x13b, subw 0x0, time 19965991, (-178,304), root:(375,724),
    state 0x10, keycode 129 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XmbLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

KeyPress event, serial 35, synthetic NO, window 0x4c00001,
    root 0x13b, subw 0x0, time 20035104, (129,285), root:(682,705),
    state 0x10, keycode 91 (keysym 0x2e, period), same_screen YES,
    XKeysymToKeycode returns keycode: 60
    XLookupString gives 1 bytes: (2e) "."
    XmbLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

[pinduvoz (pinduvoz)]

I missed the one with numeric pad.

Above "enter" key we Brazilians have a dot. Beside the same key (at left), we have a comma. The problem is that both keys are printing a comma.

So, it's confirmed here.

[Timo Aaltonen (tjaalton)]

ok, please open a new bug with xev output from the key.

[Bremm (bremm)]

Confirmed. I was thinking about "del" numpad key.

But now I'm using br_nativo instead of abnt2.

$ setxkbmap -print
xkb_keymap {
 xkb_keycodes { include "evdev(abnt2)+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+br(nativo)+inet(evdev)+level3(ralt_switch)"};
 xkb_geometry { include "pc(abnt2)" };
};

[Hebert (hebert-bernardo)]

Just to make things clear.

I just boot today's Daily-Live CD and it is not swapped.

Using ABNT2 - Br_Nativo it is a Brazilian Dvorak layout, but I guess wouldn't change the numpad outcome - the ( , ) key does'nt work at all . The dot/period ( . ) key prints a comma instead.

[Hebert (hebert-bernardo)]

ERRATA:

Is it actually printing comma also.

I forgot the hit the NUM LOCK.

My bad.

I create a new bug entry:

https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/272606

[Igor Morgado (morgado-igor)]

After Beta, Slash Quotation key is returning keycode 211 instead old 97.

Keycode 211 is mapped to I211 on keymaps

On symbols there is no reference to I211.

IS this working as intended (quotation)