Open
Description
Summary
Hello
I observe a strange behavior under Gnome on Wayland regarding Num Lock, Num pad, and Thai keyboard layout.
I have 3 languages setup, English, Thai, Japanese, and normally turn Num Lock on.
- In this state (Num Lock LED on the keyboard turned on):
- for normal gnome applications
- Numpad works on English and Japanese language layout.
- Numpad doesn't work on Thai keyboard layout.
- for browsers (Chrome)
- Numpad works on all languages.
- for normal gnome applications
- Num Lock turned off
- for normal gnome applications
- Numpad works on Thai keyboard layout.
- Numpad doesn't work on English and Japanese language layout. (Intended behavior)
- for browsers (Chrome)
- Numpad doesn't work on all languages. (Intended behavior)
- for normal gnome applications
Further more:
When I switch to non-Thai language and turn off Num Lock then switch to Thai then turn on Num Lock, the num pad will work correctly under Thai layout.
Summarize
- Under Chrome (and derivatives, like VS Code), everything works as it should on all languages.
- normal gnome apps + fcitx5 (Thai) break numpad
- there are a sequence of actions that can mitigate 2., albeit, cumbersome one.
I know, the state is kinda complicated.
I am here to clarify if needed.
How should we track down the issue?
Steps to Reproduce
- Turn num lock on and open gnome-text-editor
- type number in English layout using numpad
- switch to Thai
- use numpad again, this time the number won't show up
Expected Behavior
Num Lock + Numpad should work correctly under all circumstances.
Output of fcitx5-diagnose command
Output:
https://gist.github.com/midnight-wonderer/80d00eceda8bbc1da3fabbae3ca28795
The running application as the specimen is xed, a fork of gnome-text-editor.
Metadata
Metadata
Assignees
Labels
No labels