Possible Manual Intervention Required After xkeyboard-config 2.48-1 Update

Important notifications
21

wayland still reads that too :wink:

22

No issues here

localectl status 
System Locale: LANG=nl_NL.UTF-8 
    VC Keymap: nl 
   X11 Layout: nl 
  X11 Variant: us
23

Have read that Wayland and X11, --were X11 is still in use – still refer to localectl set-X11-keymap and that this was not changed only because of the “X11” in the name. Think it would not have made much sense to implement a “localectl set-wayland-keymap”, besides the existing “set-x11-keymap-expression”

24

So does this mean that those on wayland should also do this? For me the X11 Layout: (unset) while the System Locale: and VC Keymap: are set to the correct values.

Is there a way to know what were the values previously for X11 Layout, X11 Variant, XKBMODEL, XKBVARIANT, XKBOPTIONS etc?

I use two keyboards. One external with 78 physical keys with a layout of qwerty-us. The second is the inbuilt keyboard with a layout of qwerty-us and 80 physical keys, 81 physical keys if you count the power button key which is flush with the keyboard and next to delete key.
Both of the keyboards have a Windows/Meta/Super key and a “Fn” key which allows the F1-F12 keys to work as media control keys, scroll lock keys, and others. The “Fn” also works as a partial number keypad.
So what ideally should be the XKBMODEL, XKBVARIANT for both of these?

25

Only set system default keyboard switching needs to get setup inside your desktop session settings.
The unset x11 value is used to set correct language keymap what is used by desktop settings to set and fallback.