Bug 2239782 - Input character automatically when clicking Caps button with ibus-libpinyin input method
Summary: Input character automatically when clicking Caps button with ibus-libpinyin i...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-libpinyin
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peng Wu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-20 07:14 UTC by Lijun Li
Modified: 2023-09-26 01:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-26 01:24:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-977 0 None None None 2023-09-22 07:23:26 UTC

Description Lijun Li 2023-09-20 07:14:25 UTC 
Input character automatically when clicking Caps button with ibus-libpinyin input method

Reproducible: Always

Steps to Reproduce:
1. Install latest build with Fedora 39 WS build.
2. Add the input source of Intelligent Pinyin.
3. Type in Terminal with Intelligent Pinyin input method.
4. Click the Caps-Lock button from keyboard.
Actual Results:  
Input character automatically when clicking Caps button with ibus-libpinyin input method

Expected Results:  
Ability to input uppercase letters by normally when clicking Caps button with ibus-libpinyin input method.

Please see the attached screen-shot.
Comment 1 Lijun Li 2023-09-20 07:17:44 UTC 
Created attachment 1989646 [details]
Input character automatically when clicking CapsLock button with ibus-libpinyin input method
Comment 2 Lijun Li 2023-09-25 09:01:46 UTC 
Verified the issues is fixed on latest build, it works fine now.

lijli@fedora:~127$ rpm -qa|grep libpinyin
libpinyin-data-2.8.1-5.fc39.x86_64
libpinyin-2.8.1-5.fc39.x86_64
ibus-libpinyin-1.15.4-1.fc39.x86_64
Comment 3 Peng Wu 2023-09-26 01:24:41 UTC 
Thanks for the testing!
Note You need to log in before you can comment on or make changes to this bug.