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
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
- Physics.Raycast does not work when used on the whole model
Resolution Note (fix version 2020.2):
GTK keyboard mappings have been updated to work with the new input system.