Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2128423 - Default GTK_IM_MODULE should be ibus in GNOME Xorg
Summary: Default GTK_IM_MODULE should be ibus in GNOME Xorg
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F37FinalBlocker F37FinalFreezeException 2131673
TreeView+ depends on / blocked
 
Reported: 2022-09-20 13:44 UTC by fujiwara
Modified: 2022-10-03 08:31 UTC (History)
12 users (show)

Fixed In Version: gnome-settings-daemon-43.0-2.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2131673 (view as bug list)
Environment:
Last Closed: 2022-10-03 00:20:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-settings-daemon issues 705 0 None opened Default GTK_IM_MODULE should be ibus in GNOME Xorg 2022-09-20 13:53:54 UTC
GNOME Gitlab GNOME gnome-settings-daemon merge_requests 309 0 None opened xsettings: Always fallback to ibus 2022-09-29 22:15:23 UTC

Description fujiwara 2022-09-20 13:44:15 UTC
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

Comment 1 Jens Petersen 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.

Comment 2 Ben Cotton 2022-09-29 22:15:24 UTC
Upstream MR contains a candidate fix: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/309

Comment 3 Adam Williamson 2022-09-30 16:48:09 UTC
+3 FE in https://pagure.io/fedora-qa/blocker-review/issue/925 , marking accepted FE. Blocker voting is still open.

Comment 4 Kalev Lember 2022-09-30 19:55:33 UTC
I want ahead and backported this to gnome-settings-daemon-43.0-2.fc37 in https://src.fedoraproject.org/rpms/gnome-settings-daemon/c/619b3b7a15448a1eca9c2d90b26b1956d96af6d0?branch=rawhide

Comment 5 Fedora Update System 2022-09-30 20:09:21 UTC
FEDORA-2022-f48ce4370b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f48ce4370b

Comment 6 Fedora Update System 2022-10-01 02:13:16 UTC
FEDORA-2022-f48ce4370b 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-f48ce4370b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f48ce4370b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-10-03 00:20:33 UTC
FEDORA-2022-f48ce4370b has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.