Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
2
Found in
2020.1.4f1
Issue ID
1275964
Regression
Yes
InputSystem not mapping keyboard keys properly on Linux
Keys are not mapped correctly when using the new input system in Linux. For example:
The ',' key is mapped to ';'
The '/' key is mapped to '='
Repro steps:
1) Install the input system package.
2) Open the test input sample scene included in the package
3) Observe the keys that light up on the key map as you press different keys.
Result:
The keys that light up are not always the keys that are pressed.
Expected:
The correct keys light up.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note (fix version 2020.2):
GTK keyboard mappings have been updated to work with the new input system.