Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.71f1
6000.3.12f1
6000.4.1f1
6000.5.0b1
6000.6.0a1
Issue ID
UUM-138164
Regression
No
[Linux] Scrub cursor does not appear on numeric labels in the Grid and Snap Settings overlay after resetting it
Steps to reproduce:
- Create a new project using Universal 3D template
- In Scene View open the Grid and Snap Settings from the Grid Overlay
- Hover over and click and drag on the "Opacity" Label to modify its value to anything
- Click on the three dots in the Grid and Snap Settings
- Select "Reset"
- Hover over again over the "Opacity" label or any value with a value cursor drag
- Observe the cursor
Actual results: Cursor does not change to the scrub/arrow cursor
Expected results: Cursor changes to the scrub/arrow cursor when hovering over the “Opacity” label or other draggable numeric labels
Reproducible with versions: 2023.1.0a4, 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Tested on (OS): Ubuntu 24.04 (reproducible), macOS 26.3 (not reproducible)
Notes:
- It is still possible to modify the values by clicking and dragging, its just the cursor that does not change its state
- This issue can sometimes also be observed in other parts of the Editor, such as the Transform component, but this appears to be the easiest way to reproduce it
- Reproduction can be inconsistent
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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.