Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0b2
Issue ID
UUM-43910
Regression
No
[Linux] Scroll doesn't work when a window is attached to the left half of the secondary monitor
Reproduction steps:
1. Create a new project
2. Setup primary display on the left side, and secondary on the right side
3. Detach any window from the Unity Editor and attach it to the left half of your secondary display
4. On the primary display, set up any window on the right side of the Unity Editor that has a scroll function
5. Ensure that your mouse cursor can freely move from the primary to the secondary display
6. Attempt to scroll in the window set up in Step 4
Expected result: The scroll function within the Unity editor screen should operate as expected, allowing you to navigate up and down within the window
Actual result: The scroll function within the Unity editor does not work when there is a window attached to the left half of the second monitor.
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Reproducible on: Ubuntu 23.04
Not reproducible on: Windows 10 Pro 22H2, MacOS 13.4.1
Note: Scrolling works when the window in the secondary display is made fullscreen
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
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
Resolution Note:
After further investigation we suspect that this is a bug lies in X11 Window Manager or GNOME Desktop manager. Since looking at native GTK applications such as Gedit they behaves similar to the Linux Editor in the described scenario.