Bug 2038973 - There is a problem with the processing logic of the left SHIFT key in ibus-table
Summary: There is a problem with the processing logic of the left SHIFT key in ibus-table
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-table
Version: 35
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Mike FABIAN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-10 16:38 UTC by Bright
Modified: 2022-02-07 13:19 UTC (History)
7 users (show)

Fixed In Version: ibus-table-1.16.7-1.fc36 ibus-table-1.16.7-1.fc34 ibus-table-1.16.7-1.fc35
Clone Of:
Environment:
Last Closed: 2022-01-29 10:10:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Reproduction Video (8.18 MB, video/mp4)
2022-01-10 16:38 UTC, Bright
no flags Details
Compared (6.75 MB, video/webm)
2022-01-11 15:07 UTC, Bright
no flags Details
Fedora Silverblue (1.96 MB, video/mp4)
2022-01-11 16:20 UTC, Bright
no flags Details
fedora-silverblue-ibus-table-chinese-wubi-jidian (4.12 MB, video/webm)
2022-01-16 22:44 UTC, Bright
no flags Details

Description Bright 2022-01-10 16:38:03 UTC
Created attachment 1849893 [details]
Reproduction Video

## Description of problem:
When switching line numbers in the editor, press the left `SHIFT` key to switch the input method state, and the content between the insertion points will be selected.
The selection can only be canceled by pressing the esc key, which seriously interferes with editing work.

Version-Release number of selected component (if applicable): 
Fedora release 35 (Thirty Five)  
GNOME 41.2  
Wayland session 
ibus-1.5.25-6.fc35.x86_64  
ibus-gtk2-1.5.25-6.fc35.x86_64  
ibus-gtk3-1.5.25-6.fc35.x86_64  
ibus-libs-1.5.25-6.fc35.x86_64  
ibus-setup-1.5.25-6.fc35.noarch  
ibus-table-1.14.1-1.fc35.noarch  
ibus-table-chinese-1.8.3-11.fc35.noarch  
ibus-table-chinese-wubi-jidian-1.8.3-11.fc35.noarch  


How reproducible:
Switch to wayland session and install `ibus-table-chinese-wubi-jidian`.

Steps to Reproduce:
1. Place the cursor insertion point on the first line of text.  
2. Use the left SHIFT key to switch the input method from Chinese to English(or English to Chinese).  
3. Click anywhere on the third row to change the cursor insertion point.(can also be any line)
4. At this time, the content between the cursor insertion points in row 1 to row 3 becomes selected.

Actual results:  
The text between the insertion points is selected.   

Expected results:
Toggle insertion point only.  

Additional info:
1. I have stable reproduction on Fedora 35 LiveCD and current OS.   
2. This issue disappeared after switching to xorg session. 
3. `ibus-pinyin` doesn't have any problem in wayland session. 
4. Sometimes the content between the insertion points is not selected in the video, because the esc key is pressed.

Comment 1 Mike FABIAN 2022-01-11 13:12:41 UTC
I have the same package versions but I cannot reproduce the problem in Gnome Wayland.

Comment 2 Bright 2022-01-11 15:07:03 UTC
Created attachment 1850112 [details]
Compared

That would be weird.
Yesterday the developer of Fcitx5 said he can reproduce it too.
For comparison of three input methods based on ibus framework, see the attachment.
Do I need to provide any logs?

Comment 3 Bright 2022-01-11 16:20:44 UTC
Created attachment 1850134 [details]
Fedora Silverblue

Fedora Silverblue can also reproduce the problem, but some programs work well, such as vscode.

Comment 4 Bright 2022-01-16 22:44:07 UTC
Created attachment 1851239 [details]
fedora-silverblue-ibus-table-chinese-wubi-jidian

Hi Mike,

Can you test it again please? I can reproduce it in Fedora Workstatoin 35, Fedora 35 LiveCD and Fedora Silverblue 35. I am pretty sure that the left shift key of ibus-table is indeed the problem.

ibus-rime, ibus-libpinyin also use ibus input framework without this problem, fcitx5 does not have this problem either.

Comment 5 Eduard Vopicka 2022-01-23 18:41:18 UTC
Not sure if this is related, but when I am trying to type the dollar sign using the US keyboard layout and left shift permanently pressed and repeatedly pressing the 4/$ key, I am getting something like 444$444444444$44444444444444444 while typing to

- bash prompt in urxvt-unicode
- cat running in the same terminal
- while trying to enter URL in firefox

With the right shift, everything works well.

Comment 6 Eduard Vopicka 2022-01-23 20:03:10 UTC
Really curious if this will turn out to be related or not. Because of I am able to reproduce the problem I have described above with pure xorg and fvwm2 on top of it and with no ibus daemon running... And the 4/$ key appears to be the only to be hit by this problem from all 0-9 keys in the top row of keyboard. Andlooks like thatit is not HW problem of the keyboard because of it manifests with both notebook's built-in keyboard and external keyboard.

Comment 7 Mike FABIAN 2022-01-26 08:56:34 UTC
(In reply to Bright from comment #4)
> Created attachment 1851239 [details]
> fedora-silverblue-ibus-table-chinese-wubi-jidian
> 
> Hi Mike,
> 
> Can you test it again please? I can reproduce it in Fedora Workstatoin 35,
> Fedora 35 LiveCD and Fedora Silverblue 35. I am pretty sure that the left
> shift key of ibus-table is indeed the problem.
> 
> ibus-rime, ibus-libpinyin also use ibus input framework without this
> problem, fcitx5 does not have this problem either.

I could finally reproduce it after doing a clean reinstall of my f35 virtual machine.

And I think I could solve it:

https://github.com/mike-fabian/ibus-table/issues/98#issuecomment-1021374412

Packages for Fedora for testing are here:

https://copr.fedorainfracloud.org/coprs/mfabian/ibus-table/

You can install them like this:

sudo dnf copr enable mfabian/ibus-table
sudo dnf update ibus-table

This should install ibus-table-1.16.5-1.fc35 which has a change which seems to fix the problem.

Comment 8 Fedora Update System 2022-01-29 10:08:01 UTC
FEDORA-2022-a0115a5128 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0115a5128

Comment 9 Fedora Update System 2022-01-29 10:10:48 UTC
FEDORA-2022-a0115a5128 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-01-29 10:15:48 UTC
FEDORA-2022-a177cae607 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a177cae607

Comment 11 Fedora Update System 2022-01-29 10:16:09 UTC
FEDORA-2022-c506d63885 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c506d63885

Comment 12 Fedora Update System 2022-01-30 00:59:46 UTC
FEDORA-2022-a177cae607 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a177cae607`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a177cae607

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

Comment 13 Fedora Update System 2022-01-30 01:14:38 UTC
FEDORA-2022-c506d63885 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c506d63885`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c506d63885

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

Comment 14 Fedora Update System 2022-02-07 01:15:34 UTC
FEDORA-2022-a177cae607 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2022-02-07 01:16:21 UTC
FEDORA-2022-c506d63885 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Bright 2022-02-07 13:19:58 UTC
Thanks!


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