RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2087031 - [backport] gtk4 should prefer Wayland text input protocol over ibus-gtk4 immodule
Summary: [backport] gtk4 should prefer Wayland text input protocol over ibus-gtk4 immo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gtk4
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Carlos Garnacho
QA Contact: Radek Duda
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-17 07:32 UTC by Jens Petersen
Modified: 2022-11-15 11:44 UTC (History)
5 users (show)

Fixed In Version: gtk4-4.4.1-2.el9, gnome-settings-daemon-40.0.1-7.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:37:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-122314 0 None None None 2022-05-17 08:00:01 UTC
Red Hat Product Errata RHBA-2022:8218 0 None None None 2022-11-15 10:38:03 UTC

Description Jens Petersen 2022-05-17 07:32:06 UTC
Description of problem:
For Gnome 42 (Fedora 36) gtk4 was fixed to default to use
the Wayland input protocaol rather than the ibus-gtk4 immodule for Wayland sessions.
This bug is to request backporting these changes to RHEL9.

See https://gitlab.gnome.org/GNOME/gtk/-/issues/4699 for details.

I am not completely sure which 4.6.x release this landed in.

How reproducible:
100%

Steps to Reproduce:
1. install ibus-gtk4
2. start gtk4-demo-application
3. try to input Korean with ibus-hangul

Actual results:
3. it is not possible to enter newlines, delete input with backspace, or move the cursor with arrow keys in Hangul input mode.

Expected results:
3. Gnome Wayland should prefer the Wayland input protocol over the ibus gtk4 immodule.

Additional info:
Not that for this reason we currently don't ship ibus-gtk4 in RHEL9,
however we need it to enable ibus input in gtk4 apps under Gnome Xorg,
so fixing this is a prerequisite for shipping ibus-gtk4 in RHEL9.

Comment 6 Radek Duda 2022-07-29 10:59:47 UTC
I reproduced the bug. Then tried with new versions: 'Enter', 'Backspace' and arrow keys work now as should.

Comment 11 errata-xmlrpc 2022-11-15 10:37:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gtk4 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8218


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