Created attachment 1480776 [details] ibus-bogo-does-not-work-on-gnome-wayland.png I am trying this test case https://fedoraproject.org/wiki/QA:Bogo in Gnome Wayland on Fedora 29 installed from: Fedora-Workstation-netinst-x86_64-29-20180903.n.0.iso I type Khoong cos gif quis hown ddoocj laapj tuwj do and get: KKKhhhooonnnggg cccooossss gggiiiffff qqquuuiiissss hhhooowwwwnnn dddddddooooooocccjjjjjj lllaaaaaaapppjjjjjj tttuuuwwwwjjjj dddooo (see screenshot). But the expected result is: Không có gì quí hơn độc lập tự do The test works fine in Gnome Xorg.
It seems a regression from my patch of gnome-shell. If you delete my patch from the local build, another bug will appear. My patch is to send key events with clutter_event_put() but it seems it cannot change the keysyms against the actual typing on physical keyboard. ibus-bogo forwards three keysyms from the actual typing. E.g. If type 'a', three '`', BackSpace and 'a' are forwarded but the three keysyms are reverted to three 'a'. I have to bring back the original way to forward keycode with libxkbcommon and need to investigate how to stop the infinite loop as the original bug of bug #1611894 and bug #1625142 .
This issue is fixed in my latest patches. But there are some problems. 1. ibus-bogo uses multiple forward-key-event for one type and need to add forward-key-events for key release events in this case. 2. ibus-bogo uses forward-key-event for Latin chars but mutter uses keycode and there is no keycode for Latin chars so probably ibus-bogo needs to use ibus_engine_commit_text() instead. 3. ibus-bogo uses forward-key-event for BackSpace so if ibus_engine_commit_text() is used, the are are a time lag between forwarded a BackSpace and committed latin char. Currently I have no idea to commit a char after a key release event is done. Probably I think ibus-bogo could be simplified if forward-key-event is deleted in ibus-bogo.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.