xserver/xkb
dec05eba 5342d0c380 xkb: fix XkbGetKbdByName returning incorrect data
This is a regression first caused by 182404fde6
that sends back the old xkb data instead of the new one.
This causes a mismatch in the data and size calculations between the
XkbComputeGetMapReplySize that is called above that calculates the size
of the reply and XkbAssembleMap that sets the data for the reply.

Without this fix this error is seen when running setxkbmap fr:
"Error loading new keyboard description".

Fixes setxkbmap error described in #180

Signed-off-by: dec05eba <dec05eba@protonmail.com>
2025-06-20 10:17:10 +02:00
..
README.compiled
XKBAlloc.c
XKBGAlloc.c
XKBMAlloc.c
XKBMisc.c
XKM_file_format.txt
ddxBeep.c
ddxCtrls.c
ddxKillSrv.c
ddxLEDs.c
ddxLoad.c
ddxPrivate.c
ddxVT.c
maprules.c
meson.build
xkb-procs.h
xkb.c xkb: fix XkbGetKbdByName returning incorrect data 2025-06-20 10:17:10 +02:00
xkbAccessX.c
xkbActions.c
xkbDflts.h
xkbEvents.c
xkbInit.c
xkbLEDs.c
xkbPrKeyEv.c
xkbSwap.c
xkbUtils.c
xkbfile_priv.h
xkbfmisc.c
xkbfmisc_priv.h
xkbgeom.h
xkbout.c
xkbout_priv.h
xkbrules_priv.h
xkbsrv_priv.h
xkbtext.c
xkbtext_priv.h
xkmread.c

The X server uses this directory to store the compiled version of the
current keymap and/or any scratch keymaps used by clients.  The X server
or some other tool might destroy or replace the files in this directory,
so it is not a safe place to store compiled keymaps for long periods of
time.  The default keymap for any server is usually stored in:
     X<num>-default.xkm
where <num> is the display number of the server in question, which makes
it possible for several servers *on the same host* to share the same 
directory.

Unless the X server is modified, sharing this directory between servers on
different hosts could cause problems.