When using "include" in compat, previously set group compatibility modifiers are reset, even if the included compat file makes no specification for them. This is a xkbcomp bug (in my understanding). xkeyboard-config currently runs into this bug in compat/basic. Changing the "include" to "augment" in compat/basic circumvents this. Avoiding the bug restores user's to set up a keyboard mapping that works with non-XKB-able relatively easily with xmodmap. Signed-off-by: Andreas Wettstein --- compat/basic | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/compat/basic b/compat/basic index 393c324..70399c7 100644 --- a/compat/basic +++ b/compat/basic @@ -38,8 +38,8 @@ default xkb_compatibility "basic" { group 3 = AltGr; group 4 = AltGr; - include "ledcaps" - include "lednum" + augment "ledcaps" + augment "lednum" indicator "Shift Lock" { !allowExplicit; whichModState= Locked; -- 1.7.6