Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
3
Found in
2019.4
Issue ID
1280104
Regression
Yes
[Linux] Keypad number keys reporting incorrectly
Accidental regression due to recent changes.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
alfish
Oct 05, 2020 18:04
Similar bug in Input System package: https://forum.unity.com/threads/how-can-i-enable-active-polling-to-workaround-this-gamepad-drift-bug.978897/#post-6358926
The keys are mapped all wrong in the Editor Player (runtime works). It doesn't seem to be a keyboard layout problem, as it also happens in US layout. Kubuntu 20.04, Unity 2020.1.4f1.