Bug 1897782

Summary: ibus pinyin input with special characters like '/' will repeat itself non-stop and cause strange behaviours with background applications
Product: [Fedora] Fedora Reporter: Yang Wentao <yemoran-2020>
Component: ibus-libpinyinAssignee: Peng Wu <pwu>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: hujq, i18n-bugs, petersen, pwu, tfujiwar, yemoran-2020
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 14:11:28 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:

Description Yang Wentao 2020-11-14 12:16:38 UTC 
Description of problem:

In Fedora 33 Workstation, with a Chinese system language, when I try to input with the ibus input (intelligent pinyin), and I pressed the slash key'/', then the slash character '/' will automatically keep repeating itself, even if I only pressed the slash key '/' once. 

Not only this caused unwanted '/' to spam, but: 
1. Also prevents me from pressing alphabetical characters to use pinyin input normally, unless I delete all my remaining characters to exit pinyin prompt and start over;
2. Can possibly delete my already-saved text, in combination with <Ctrl-Backspace>. 
It seems that I have completely lost control within the pinyin prompt. I have met with other surprising conditions, though cannot be immediately reproduced now, but I believe more combinations of inputs triggering different bugs will be confirmed later.

Version-Release number of selected component (if applicable):
Any kind of version. I also tested with Fedora 32 Workstation, still have this bug.

How reproducible:
Always


Steps to Reproduce:
1. Fetch any Fedora Workstation version, be it 32 or 33 or any updates applied.
2. Add Chinese input method 'Intelligent Pinyin' and switch to it
3. In GNOME(Wayland), open any GTK-based application, be it Firefox, GNOME Terminal, gedit, Libreoffice, ... (take gedit as an example)
4. Input 你好，今天天气 (keypress: nihao<1>，jintian<1>) as a start up example, confirm input use number key '1'. or keys like <Enter> or <Space>.
5. Input 怎么样/ (keypress: zenmy/）. Do not confirm immediately after 'zenmy', but press '/' exactly once.
6. The '/' character is repeating itself within several hundred milliseconds.
7. Press <Ctrl-Backspace>. gedit will highlight "你好，今天天气" (with a lot of trailing '/').
8. Press <Backspace> to delete these Chinese characters.

Actual results:
Not only '/' is repeating itself, but also I lost control to gedit and gedit thinks you want to press '/' forever or even wants to delete my already-confirmed characters before this input.

Expected results:
1. '/' Should not trigger anything, unless I have pressed this key and did not release this key press (but I always release keys)
2. '/' Should not make me lost control over pinyin prompt to gedit
3. <Backspace> Should only delete pinyin alphabets in pinyin prompt panel, and should not do anything to the background gedit texts, unless I have exited the pinyin prompt panel (because I confirmed my input or have deleted every pinyin alphabet in it) 

Additional info:
1. I did not found this bug on Debian buster or Arch with latest updates. Additionally, '/' did not even input a single character '/' in these distributions, but I cannot confirm if this is the expected behaviour. In Fedora 33 KDE, '/' did input a single character '/', but immediately stopped.
2. I didn't find this behaviour in qt-based applications (like Fedora Image Writer or Octave) in GNOME, or any application in other desktop environments (including KDE, or even GTK-based Cinnamon Desktop). This bug seems to only occur on GTK-based applications on GNOME.
3. I can be very sure that this is not caused by something wrong with my specific keyboard, because (a) Other distributions worked very well (b) Other Fedora spins worked very well (c) Qt-based applications in GNOME worked very well (d) GNOME X11 session worked very well (e) I replicated this bug on a fresh install of Fedora 32 Workstation in another laptop of mine.
4. I guess other special characters (or keys) like '[', ']', '\', '<Esc>', '<Backspace>', etc. may trigger similar bugs, but I cannot confirm. '/' will surely trigger this. ',' and '.' are used in pinyin input method to flip candidate characters pages, so they doesn't trigger this bug. ' does not trigger this bug (used in xi'an for 西安)
Comment 1 Yang Wentao 2020-11-14 12:28:46 UTC 
This bug doesn't seem to affect KDE, no matter it's a Wayland session or X11 session.
Comment 2 Yang Wentao 2020-11-14 12:31:31 UTC 
In short, it's a very subtle bug, which only affect "Fedora Workstation's GNOME Wayland session and GTK-based applications", not anything else. I have been deeply confused about this, ONLY the combiation will trigger this bug.
Comment 3 Yang Wentao 2020-11-14 17:15:17 UTC 
(In reply to Yang Wentao from comment #1)
> This bug doesn't seem to affect KDE, no matter it's a Wayland session or X11
> session.

My mistake, I test for Plasma(Wayland) again and on wayland session ibus-libpinyin simply does not work entirely. It does displays an icon, but nothing afterwards. 
Looks like this bug may also be wayland-related.
Comment 4 Peng Wu 2020-11-23 09:09:20 UTC 
Could you try to test the pinyin input method with new user account or with Fedora Workstation Live iso?
Comment 5 Yang Wentao 2020-11-28 08:22:50 UTC 
(In reply to Peng Wu from comment #4)
> Could you try to test the pinyin input method with new user account or with
> Fedora Workstation Live iso?

I tried the pinyin input method with a new user account on my existing fedora installation, and I also tried the pinyin input method with a Fedora Workstation 33 Live iso (which is possible, because GNOME settings allows you do that even in Live iso). This bug still persists.
Comment 6 Ben Cotton 2021-11-04 16:54:10 UTC 
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 7 Ben Cotton 2022-05-12 16:24:53 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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.
Comment 8 Ben Cotton 2023-04-25 16:41:12 UTC 
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.
Comment 9 Peng Wu 2024-02-06 02:04:09 UTC 
I think this bug is improved in Fedora 39.
Comment 10 Parag Nemade 2024-03-18 03:35:55 UTC 
Is this still happening on any of F38+ releases?
Comment 11 Aoife Moloney 2024-05-07 15:42:58 UTC 
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.
Comment 12 Aoife Moloney 2024-05-21 14:11:28 UTC 
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.
Comment 13 Red Hat Bugzilla 2024-09-19 04:25:08 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days