Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133287
Regression
No
[Linux] UI Builder Material icon is pixelated in the Material field
Reproduction steps:
1. Create a new project
2. Create > UI Toolkit > UI Document
3. Double-click on the newly created Asset to open UI Builder window
4. Drag and drop any of the Elements into the Hierarchy
5. Expand Material foldout in the Inspector
6. Select any of the Materials and observe the Material field
Actual result: Material icon is pixelated
Expected result: Material icon is not pixelated
Reproducible with: 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Couldn’t reproduce with: 6000.0.66f2 (No Material field)
Reproduced on: Ubuntu 24.04
Not reproduced on: Windows 11, macOS Sequoia 26.2 (M4)
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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.5.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.