On Fri, Dec 15, 2017 at 04:43:47PM +0100, Olivier Fourdan wrote:
> When the Wayland compositor notifies of a new keymap, for the first X11
> client using the keyboard, the last slave keyboard used might still not
> be set (i.e. “lastSlave” is still NULL).
>
> As a result, the new keymap is not
When the Wayland compositor notifies of a new keymap, for the first X11
client using the keyboard, the last slave keyboard used might still not
be set (i.e. “lastSlave” is still NULL).
As a result, the new keymap is not applied, and the first X11 window
will have the wrong keymap set initially.