Sending the switch state change twice within the same frame is invalid
evdev protocol and only works if the client handles keys immediately as
well. Processing events immediately is incorrect, it forces a fake
order of events that does not exist on the device.

Recent versions of libinput changed to only process the device state and
SYN_REPORT time, so now the key event is lost.

https://bugs.freedesktop.org/show_bug.cgi?id=104041Signed-off-by: NPeter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: NDarren Hart (VMware) <dvhart@infradead.org>