+++ This bug was initially created as a clone of Bug #2128423 +++ Now GNOME Xorg sets GTK_IM_MODULE to "ibus" in some Asian locales using /etc/X11/xinit/xinitrc.d/50-xinput.sh but "gtk-im-context-simple" in other locales. But previously GNOME Xorg sets GTK_IM_MODULE to "ibus" in all locales. Probably a GNOME desktop module always can set the default GTK_IM_MODULE in GNOME Xorg. To reproduce: 1. Log into GNOME Xorg in en_US.UTF-8 locale 2. Run `ibus im-module` "gtk-im-context-simple" is output. Expected result: "ibus" is output. Note: GTK_IM_MODULE="wayland" in GNOME Wayland by default now --- Additional comment from Jens Petersen on 2022-09-29 03:27:49 UTC --- This means in particular that if you try to add a first input method in gnome-control-center you need to restart gnome in order for it to work properly, which is not a great experience (unlike in Wayland where the input method just works immediately). Strictly speaking this regression started actually in F36 (Gnome 42) I believe. But we feel it is actually a potential blocker bug. Though this is not resolved yet upstream.
I think /etc/X11/xinit/xinitrc.d/50-xinput.sh also needs to be updated. Currently the script sets GTK_IM_MODULE=gtk-im-context-simple in en_US.UTF-8 locale in GNOME Xorg.
Discussed during the 2022-10-03 blocker review meeting: [1] The decision to punt the decision on the blocker status was made: "We want more info on this bug before we vote (particularly regarding Xorg and if it is default config anywhere), so we will punt for now." [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-10-03/f37-blocker-review.2022-10-03-16.00.log.txt
FEDORA-2022-80327b0c8a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-80327b0c8a
FEDORA-2022-80327b0c8a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-d5a9bcdac5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d5a9bcdac5
FEDORA-2022-40db8f5e7d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-40db8f5e7d
FEDORA-2022-d5a9bcdac5 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d5a9bcdac5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d5a9bcdac5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-40db8f5e7d has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-40db8f5e7d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-40db8f5e7d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d5a9bcdac5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-40db8f5e7d has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
Dear developers. I'm using Fedora 36 (KDE spin) and fcitx5. Recently i upgraded imsettings from imsettings-1.8.3-2.fc36 to imsettings-1.8.3-6.fc36. This change makes imsettings not work properly under KDE/Wayland. I run `imsettings-switch -f fcitx5` to setting im forcely and then restart. However the behavior is that imsettings-daemon starts, the fcitx5 starts, but i could not trigger input methods. The `XMODIFIERS` `GTK_IM_MODULE` `QT_IM_MODULE` are still xim or gtk-im-context-simple:xim or @im=none in the environment. I found thess environments are set in `~/.config/environment.d/imsettings*.conf`, I have to edit these configs manually to fcitx5 (and then works). I have tested that remove `~/.config/environment.d/imsettings*.conf` these files and restart will not work ( resulting `XMODIFIERS` `GTK_IM_MODULE` `QT_IM_MODULE` missing in environment). The line in the patch https://src.fedoraproject.org/rpms/imsettings/blob/4534b0727bdf875ea02e8c4bbab895f6957dd300/f/imsettings-disable-gnome.patch `rm -f $XCONFIGDIR/environment.d/imsettings*.conf || :` seems not work too . The reason i guess is that Wayland do not source the scripts under /etc/X11/xinit/xinitrc.d/ so the `~/.config/environment.d/imsettings*.conf` not removed and `XMODIFIERS` `GTK_IM_MODULE` `QT_IM_MODULE` are not set. Ref: https://wiki.gnome.org/Initiatives/Wayland/SessionStart (saying: The wayland session is not running a login shell and is not sourcing /etc/X11/xinit/xinitrc. ) So i hope that there's a better way to handle the drop of systemd backend. Thanks.
See https://bugzilla.redhat.com/show_bug.cgi?id=2157582 and updates for f36 will be available shortly in updates-testing.