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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 2020.2):
GTK keyboard mappings have been updated to work with the new input system.