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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
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.