[xkb] 1dk layer is replaced by AltGr layer when used along Xkb-config Bépo or system-installed Optimot

[nivopol]

On an XOrg setup :

• install a 6-level layout such as Ergo‑L into /usr/share/X11/xkb/symbols/custom
• configure it along with X-included Bépo or Optimot 1.7.

Now 1dk act as a AltGr layer latch and not a 1dk-typo layer.

[nivopol]

First thing first, this issue is linked to #118 as this behaviour comes from the interaction between the 1dk implemented with <MDSW> and other layouts binding it to Mode_switch.

The big difference is here it’s not even an issue of loading order forcing default key binding. These combination are always broken.

[nivopol]

Explanation

Optimot and Bépo are including pc(pc105) symbols. Bépo is the only Xkb-include French layout to do this, and basically this seems limited to a few old hardware-specific configuration.

Consequences

pc105 is the default symbols statement in pc file, so it is the culprit for #118, and it makes sense to:

• patch Kalamine so the generated drivers work around this default to solve #118
• patch Xkb-config to play nicer with modern layouts, which was done in June 2022 due to Neo project action, as explained in #118.

Nevertheless, as inconsequential as it’ll shortly become, we have here a specific Bépo bug, which could have other side effects in the future. Optimot inherited it.

Optimot solution

Optimot is non-free, and doesn’t have public repository and ticketing. Development team was made aware of the bug and it will be fixed in upcoming 1.8 version.

Bépo solution

Bépo is old and quite poorly technically maintained due to lack of developer on the project for some times. There is nevertheless a ticketing system at Bépo’s Gitlab and a buglist on Bépo’s wiki. The relevant ticket will be created ASAP, as we are waiting hints on preferred channel and needs by the Bépo team.

The issue concerns Xkb-config, so it should be passed on their system. Note that there is already a related issue opened, which would imply that soon all layouts will have Bépo behaviour, except pc105 was patched in-between so no worry.

[wismill]

@nivopol Bépo issue already fixed in xkeyboard-config, bug should be reported to the Bépo repository.

[nivopol]

I should have F5, thanks.

[wismill]

Update: Fixed in Optimot 1.8 and Bépo (xkeyboard-config-2.42, to be published in about 3 months).

We still need a fix for configurations with older xkeyboard-config (≤ 2.41).