Search Issue Tracker
Fixed
Fixed in 2020.3.X, 2020.3.47f1
Votes
0
Found in
2020.3.45f1
Issue ID
UUM-29806
Regression
No
[Linux][Input System] Crash on "GetGameControllerMapping(void*)" when Gamepad is connected
Reproduction steps:
1. Create a new Project and open it
2. Open the Edit > Project Settings > Player Window
3. Under “Other Settings” set “Active Input Handling” to “Input System Package (New)”
4. Connect a Gamepad to your computer
Expected result: New Input System reads Gamepad’s controls
Actual result: Unity Editor crashes
Reproducible with: 2020.3.45f1, 2021.2.16f1
Not reproducible with: 2021.3.20f1, 2022.2.8f1, 2023.1.0b6, 2023.2.0a4
Fixed in: 2021.2.17f1
Reproducible on: Ubuntu 22.04.2
Not reproducible on: Windows 10
FIrst lines of stack trace:
0x007effc5842520 in __sigaction
0x007effc59b223c in __nss_database_lookup
0x0055d1de766860 in GetGameControllerMapping(void)
0x0055d1de760062 in SDLGamepadDeviceDescriptor::SDLGamepadDeviceDescriptor(int)
0x0055d1de75e0a4 in ReportNewSDLController(void)
Note:
- From tested gamepads, only Xbox 360 controllers cause Unity Editor to crash
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment