Good. Then let me try to explain the nature of the problem you encountered.
It's not really an ibus issue. But GNOME integrates ibus into its desktop, and this is about the way they do so. ibus is started and configured by default in GNOME desktops. But for some reason they have an on/off mechanism for GTK, so for a user who does not have any ibus input methods enabled (and does not make use of the on-screen keyboard) ibus is turned "off" for GTK applications. By adding "Intelligent Pinyin" to your list of input sources you turned ibus "on" and it started to work as expected. Can't tell why you don't see the issue with Chrome. Maybe Chrome somehow ignores the GNOME on/off thing. At the release of Ubuntu 22.04 there was a related issue, which I reported upstream: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682 I mention that because Carlos Garnacho's reply includes a description of how the mechanism is thought to work. I can't help wondering how this relates to your app. In a previous comment you let me know that your "app relies on compositionend events". But if I understand it correctly, "compsitionend" is only used that way if ibus is running. Is your app an ibus app, but it fails to tell the system? Or is it a non-ibus app which still is relying on an ibus specific mechanism with respect to dead keys composing? Have you tried to run your app on a desktop where ibus is not present at all? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #682 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682 ** Package changed: ibus (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1999207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
