Bug 1936380 - backspace key etc not working in gtk4-demo with the ibus-gtk4 immodule+IME
Summary: backspace key etc not working in gtk4-demo with the ibus-gtk4 immodule+IME
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 34
Hardware: Unspecified
OS: Other
unspecified
unspecified
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1989951
TreeView+ depends on / blocked
 
Reported: 2021-03-08 10:53 UTC by Priyam Gupta
Modified: 2021-08-12 01:49 UTC (History)
8 users (show)

Fixed In Version: ibus-1.5.24-13.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1989951 (view as bug list)
Environment:
Last Closed: 2021-08-12 01:49:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gtk issues 3465 0 None None None 2021-03-11 02:44:33 UTC

Description Priyam Gupta 2021-03-08 10:53:25 UTC 
Description of problem:


How reproducible:


Steps to Reproduce:
    1.Install ibus-gtk4 and gtk4-devel packages.
    2.Enable an input method engine
    3.Run gtk4-demo
    4.Select "Entry" -> "Completion" in the left pane
    5.Click "Run" button in the top
    6.Focus on the input entry and type a language string.
    7.Try to press backspace.

Actual results:
   Backspace key does not working

Expected results:
   Backspace key should work

Additional info:
Comment 1 Jens Petersen 2021-03-10 09:41:07 UTC 
Thanks, Priyam

It seems related to the ibus-gtk4 immodule.
At least if I disable all IMEs or remove ibus-gtk4
then gtk4 input works normally again.
Comment 2 Jens Petersen 2021-03-10 09:43:14 UTC 
(I used Text View -> Multiple Views to avoid any other input completion feature.)
Comment 3 fujiwara 2021-03-11 02:46:29 UTC 
Probably this will be a limitation until the solution is found.
Comment 4 fujiwara 2021-08-12 01:49:09 UTC 
After the upstream discussion, I enable a sync key process key events.
Other issues should be reported separatedly.
Note You need to log in before you can comment on or make changes to this bug.