Bug 2124007

Summary: Keyboard disappears from list of installed keyboards
Product: [Fedora] Fedora Reporter: Ben Engbers <Ben.Engbers>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: adscvr, development.group, fmuellner, gnome-sig, i18n-bugs, jadahl, otaylor, tagoh, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-17 09:28:31 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 Ben Engbers 2022-09-03 21:22:31 UTC
Description of problem:
I have installed 3 keyboards (English VS, English International and Anthy). Anthy is mostly used in Libre Office Writer 7.3.4.2. I can switch the keyboard either by selecting one in the upper right corner of the screen or by cycling through te list of installed keyboards with Windows key/spacebar.

After a few minutes my Lenovo laptop goes to sleep automatically. When I wake it up again, the Anthy keyboard has disappeared from the list of keyboards. Only the 2 English keyboards can be selected. In the settings dialog however, the Anthy keyboard is still visible.
It is only after a new logon that the Japanese keyboard shows up again.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Logon after boot
2. Wait till the laptop goes to sleep
3. Wake up.

Actual results:
Anthy keyboard is no longer visible


Expected results:
Anthy keyboard can not be selected


Additional info:

Comment 1 Jens Petersen 2022-09-05 02:34:17 UTC
I think this is bug 2062619

Comment 2 Akira TAGOH 2023-04-17 09:28:31 UTC

*** This bug has been marked as a duplicate of bug 2062619 ***