Olivier Fourdan 16fd18479d xwayland: avoid race condition on new keymap ... 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. Apply the new keymap to the master keyboard as long as there's one. Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=791383 Signed-off-by: Olivier Fourdan <ofourdan@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 170c959785)		2018-01-22 14:06:44 -05:00
..
dmx	Unvalidated lengths	2017-10-12 12:25:02 -04:00
kdrive	xephyr: Check for host XVideo support before trying to use it	2017-09-22 18:45:59 +02:00
vfb	Remove fd_set from Block/Wakeup handler API	2016-07-18 15:27:51 -04:00
xfree86	edid: fix off-by-one error in CEA mode numbering	2017-12-13 10:07:17 -05:00
xnest	Remove fd_set from Block/Wakeup handler API	2016-07-18 15:27:51 -04:00
xquartz	glx: Fix glXQueryContext for GLX_FBCONFIG_ID and GLX_RENDER_TYPE (v2)	2017-12-13 10:08:40 -05:00
xwayland	xwayland: avoid race condition on new keymap	2018-01-22 14:06:44 -05:00
xwin	hw/xwin: Add 'dri' to DIST_SUBDIRS	2016-09-16 10:57:23 -07:00
Makefile.am	Xwayland DDX	2014-04-03 15:19:22 -07:00