Search Issue Tracker
Fixed in 2022.3.18f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0b2, future release
Votes
2
Found in
2022.3.14f1
2023.2.2f1
2023.3.0a16
Issue ID
UUM-57233
Regression
Yes
[Linux] CursorLockMode.Confined does not confine cursor when using multiple displays
Reproduction steps:
1. Open the attached ”CursorBug” project
2. Click File > Build
3. Launch the built Player
4. Move the cursor in the direction of a secondary display
5. Observe the behavior of the cursor
6. Click LMB somewhere in the Player
7. Move the cursor in the direction of a secondary display
8. Observe the behavior of the cursor
9. Move the cursor back into the Player
10. Repeat 4th step
Expected result: The cursor is always confined in the Player fullscreen window
Actual result: The cursor is not confined anymore after clicking/holding LMB
Reproducible with: 2022.3.14f1, 2023.1.0a11, 2023.1.24f1, 2023.2.2f1, 2023.3.0a16
Not reproducible with: 2021.3.33f1, 2023.1.0a10
Reproducible on: Ubuntu 23.10, Ubuntu 22.04
Not reproducible on: Windows 11 (User tested)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Add comment