Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.21f1
Issue ID
UUM-82921
Regression
No
[Ubuntu] GUIUtility error when cancelling Extract Materials window
Steps to reproduce:
- Open a Unity project
- Import [https://assetstore.unity.com/packages/3d/characters/ghoul-zombie-114531] to your project (any model will do but this is a small file sized one)
- Select the imported model (Ghoul@Animations.fbx in the above case)
- On the Import Settings, navigate to the Materials tab
- Click on 'Extract Materials'
- Click Cancel on the window that opens
Actual results: An 'EndLayoutGroup: BeginLayoutGroup must be called first' error is logged to console.
Expected results: No errors are logged to console.
Reproducible with versions: 6000.0.21f1, 2022.3.47f1
Not reproducible with versions: -
Can’t test with versions: 2021.3.44f1 (can't load version as unsupported)
Tested on (OS): Ubuntu 24.04
Notes:
- Only appears to occur on Ubuntu. Have tested on Windows and no error is logged to console.
- If error doesn't occur, re-open Extract Materials and close it again. Sometimes it only occurs
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.