Latest xkeyboard-config (2.39-1) and Dvorak layout

Jon Turney jon.turney@dronecode.org.uk
Mon Jun 19 11:05:39 GMT 2023


On 19/06/2023 03:39, Nem W Schlecht via Cygwin wrote:
> Just did a Cygwin update on my Windows 10 box and after restarting X11 I
> found the keyboard layout switched back to the default (Qwerty) from my
> normal (Dvorak).
> 
>  From the X11 logs:
> [2516952.656] (--) Setting autorepeat to delay=500, rate=31
> [2516952.656] (--) Windows keyboard layout: "00010409" (00010409) "United
> States-Dvorak", type 4
> [2516952.656] (--) Found matching XKB configuration "English (USA,Dvorak)"
> [2516952.656] (--) Model = "pc105" Layout = "dvorak" Variant = "none"
> Options = "none"
> [2516952.656] Rules = "base" Model = "pc105" Layout = "dvorak" Variant =
> "none" Options = "none"
> 
> *[2516952.859] (EE) Error loading keymap /tmp/server-0.xkm[2516952.859]
> (EE) XKB: Failed to load keymap. Loading default keymap instead.*
> [2516953.078] winInitMultiWindowWM - DISPLAY=:0.0
> [2516953.078] winMultiWindowXMsgProc - DISPLAY=:0.0
> 
> So, this *isn't* the old culprit of xkbcomp not working, because there is
> no error there.
> 
> I reverted back to 2.37-1 of "xkeyboard-config" and everything is working
> fine again, so it is the culprit in some way.

Thanks for reporting this.

This seems to be due to a change in xkeyboard-config [1]

It looks like I need to update the table which maps from Windows to XKB 
keyboard layouts (so that US dvorak maps to layout=us variant=dvorak, 
rather than just layout=dvorak), which is built into the X server.

As a workaround in the meantime, you can use an explicit 'setxkbmap us 
dvorak', or keep on downgrading xkeyboard-config.

[1] 
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/391



More information about the Cygwin mailing list