GTK3 apps on Wayland don't always follow text_input_v3 (race condition)
While testing a GTK application in a Plasma Mobile environment, we've been experiencing a race condition with GTK applications where GTK won't accept any input from a virtual keyboard. Running for example gedit with
WAYLAND_DEBUG=1 revealed that it doesn't even try to use the
text_input_v3 Wayland protocol/extension, which would explain this. This only happens with GTK applications, I tried Qt applications and the text-input example from wlroots as well, and not every time. 50% of the time after booting it'll work fine, only for it to break again the next reboot.
This bug was first seen with GTK 3.24.28, but after some testing has been happening for longer, I tested every lower version up to 3.24.23. Experienced on postmarketOS (Alpine Linux) with distribution packages, but also with self-built packages on the system itself.