[Bug 2013610] Problem when ibus uses XIM: When committing something and then sending a space by returning False, the commit and the space are reversed

https://bugzilla.redhat.com/show_bug.cgi?id=2013610



--- Comment #4 from fujiwara <tfujiwar(a)redhat.com&gt; ---
Currently ibus-x11 works with sync key events by default since Java X11 clients
causes SEGV with async key events and some X11 applications spend time and does
not work with async key events.
Unfortunately libX11 does not sort key events with the time values.


https://github.com/ibus/ibus/commit/b58351ec2f7c057dcfe0aff883064039702a56d7
https://github.com/ibus/ibus/issues/1713
https://github.com/ibus/ibus/issues/1847

The workaround is to run ibus-daemon --xim with IBUS_ENABLE_SYNC_MODE=0 .

On the other hand, I suggest to delete forward-key-event API to handle FALSE
key events in GTK4.

Those requests are conflicted now by each other.

Solution #1
- Delete forward-key-event in each ibus engines to handle FALSE key events
- Ask each Java applications to cause SEGV with async key events
- Bring back async key events to ibus-x11

The risk is that we don't touch each Java applications and depends on the Java
developers efforts


Solution #2
- Change focus-in API in IBus engines to get the client names and context names
to handle the forward-key-event API by client names

The risk is that each IBus engine need to change focus-in API between IBus
versions.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013610