[kde] [Bug 474936] New: Switching keyboard lay-out has no effect in Steam games
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Wed Sep 27 14:37:13 BST 2023
https://bugs.kde.org/show_bug.cgi?id=474936
Bug ID: 474936
Summary: Switching keyboard lay-out has no effect in Steam
games
Classification: I don't know
Product: kde
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: kravanjunk at protonmail.com
Target Milestone: ---
I generally use the Belgian (azerty) keyboard lay-out. For some games I switch
the lay-out to US (qwerty) with a short-cut but the game does not recognize the
switch and continues to use the azerty lay-out UNLESS I open the keyboard
lay-out section and move the US qwerty lay-out above the Belgian azerty one and
hit apply.
Then the game will start recognizing my inputs in qwerty.
I've always used the global switching policy and that didn't work, other
switching policies also had no effect.
STEPS TO REPRODUCE
1. Start a game in Steam (I tested Batman: Arkham Asylum and Origins)
2. Test out the keyboard to confirm it's azerty/qwerty
3. Use the shortcut to change to qwerty/azerty
4. Notice there's no difference
5. Alt-tab and change the order of the keyboard lay-outs in keyboard system
settings
6. Go back into the game and notice the lay-out listed at the top in keyboard
systeml settings is now being recognized by the game
EXPECTED RESULT
The expected result would be that if I change the keyboard lay-out by using the
shortcut and the OSD shows my lay-out has switched that the game now uses the
new keyboard lay-out.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Unsure if this matters but I'm using Wayland.
ADDITIONAL INFORMATION
I think a possible solution could be that changing the lay-out by shortcut also
re-arranges the keyboard lay-out order, but I'm not a developer.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list