SUMMARY > GTK relies on the Wayland text protocol and compositor-side input method support. > If this isn't working for you, then either your compositor > does not support the text protocol (unlikely), > or it does not have any input method support that handles compose sequences > That's something you need to raise with those compositors. Apparently KWin does not support it? Please see the closed issue https://gitlab.gnome.org/GNOME/gtk/-/issues/7740 Offending commit on Gtk's side: https://gitlab.gnome.org/GNOME/gtk/-/commit/621b7facc8b098811f659a0cba56d27e6ae39ea2 STEPS TO REPRODUCE 1. Open any Gtk application running against Gtk 4.20 2. Try to enter a char with an accent such as á in an input field OBSERVED RESULT a is typed This is for sure a huge problem for languages, which rely on accent keys. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20251013 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Graphics Platform: Wayland
KWin absolutely supports input methods, you're just not using one. If GTK requires you to use one for simple compose sequences, that may be surprising and IMO a bad move, but not something we have any influence over.
> compositor does not support the text protocol Just to clarify this point, we do support all the Text Input Protocols. > or it does not have any input method support that handles compose sequences No, because that's an expectation change they've made without any co-ordiantion or testing. This is 100% a GTK created mess, and we're not doing anything wrong, but given it affects users it might be fastest for us to be the ones to dig everyone out of it.
Thank you for your response. > given it affects users it might be fastest for us to be the ones to dig everyone out of it. Just to understand you correctly: Does this mean you will adapt something on Kwin's side or is having set up an input method from now on the only and permanent solution if one uses Gtk4 applications? Thanks in advance!