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.
Comments (1)
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"
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.