Files
Alexander Melnyk 36a7fdd315 xkb: Fix locked/latched indicator desync across multiple keyboards
When a group indicator (or a latched indicator of any kind) is defined,
e.g.:
  indicator "Scroll Lock" { groups = Group2; }
the logical and physical indicator state may desync across multiple
connected keyboards.

This is caused by XkbPushLockedStateToSlaves only pushing locked_mods to
the slave devices. Pushing locked_group (as well as latched groups/mods)
along with locked_mods resolves the issue.

The issue is not observed with API calls because a different code path
is taken (avoiding XkbPushLockedStateToSlaves altogether).

Signed-off-by: Alexander Melnyk <inboxnumberzero@zoho.com>
Part-of: <https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/2120>
2026-01-28 03:31:19 +02:00
..
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00
2022-07-08 14:27:04 +00:00
2024-10-10 13:38:31 +00:00
2017-10-30 13:45:20 -04:00
2024-10-10 13:38:31 +00:00
2024-10-10 13:38:31 +00:00

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.