Bug 2098250
Summary: | Tab key does not reach input method when using gnome-text-editor with GTK_IM_MODULE=ibus | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike FABIAN <mfabian> | ||||
Component: | gtksourceview5 | Assignee: | Kalev Lember <klember> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 38 | CC: | gnome-sig, klember, link, mclasen, mfabian, ngompa13, pwu, tfujiwar, wt | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | gtksourceview5-5.12.0-1.fc40 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2024-05-21 14:14:24 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
When the wayland input is used instead of the GTK4 input module, this problem does not occur. I.e. when using a Gnome Wayland session and starting gnome-text-editor like this: env -u GTK_IM_MODULE gnome-text-editor then the Tab key event is correctly processed by the event processing of the input method. This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Sorry for the late response. I checked the attached video with my mobile phone and report my thoughts to the upstream. Yes, the problem is unchanged in f38. I also just tested it again. There is a similar problem in kde now as well. Should the /etc/X11/xinput.d/ibus script be changed to not set QT_IM_MODULE or GTK_IM_MODULE when running under Wayland? (In reply to Wren Turkal from comment #5) > There is a similar problem in kde now as well. Should the > /etc/X11/xinput.d/ibus script be changed to not set QT_IM_MODULE or > GTK_IM_MODULE when running under Wayland? This is a GTK application issue. If you use GNOME Wayland, you should unset GTK_IM_MODULE and gnome-settings-daemon will set GTK_IM_MODULE=wayland and it works. If you use Plasma Wayland, IBus did not support the Wayland protocol in Fedora 28 but now works with systemsettings5 and unset GTK_IM_MODULE in Fedora39. This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. 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 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. Verified fixed the issue. |
Created attachment 1890961 [details] Video showing how the Tab key is used by gnome-text-editor and doesn’t reach the event processing of the input method - gnome-text-editor-42.2-1.fc36.x86_64 - Gnome Wayland or Gnome Xorg session - GTK_IM_MDOULE=ibus set in the environment - Start gnome-text-editor - Try to use any ibus input method, for example ibus-anthy as shown in the attached video - When using ibus-anthy, type “a” to get a hiragana “あ” - Type space to convert to kanji, the preedit shows “唖” (or another kanji with that pronunciation) - Type space again to open the candidate list and show the second candidate - Type Tab to select the next (3rd) candidate) => Now, instead of selecting the first candidate, the preedit and the candidate list move one tabulator width to the right. The input method does not see the Tab key event at all. When I use ibus-typing-booster instead of ibus-anthy, increase the debug level to 3 in the setup tool, and check the debug log like this: [mfabian@fedora ~]$ tail -F .local/share/ibus-typing-booster/debug.log | grep process_key_event I see nothing in the debug log when Tab is pressed, i.e. the key event doesn’t reach the input method. See attached video.