Search Issue Tracker
Third Party Issue
Votes
2
Found in
2021.3.36f1
2022.3.22f1
2023.2.15f1
6000.0.0b12
7000.0.0a1
Issue ID
UUM-67031
Regression
No
[Linux] Floating windows do not keep their size after restarting the Editor
Reproduction steps:
1. Create a new 3D project
2. Open the Package Manager window (Window > Package Manager)
3. Open the Profiler window (Window > Analysis > Profiler)
4. Make sure both of those windows are undocked
5. Resize both of those windows
6. Close and re-open the Editor
7. Observe the floating windows
Expected result: The floating windows keep their sizes
Actual result: The floating windows go back to their default sizes
Reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12
Reproducible on: Ubuntu 23.10
Not reproducible on: Ubuntu 22.04, Windows 10
Notes:
- The Editor sometimes starts minimized when it was closed while being full screen
- 2021.3 - Few floating windows did keep their size (ex: Package Manager), but some did not (ex: Profiler)
Comments (3)
-
TimGS
Aug 09, 2024 20:06
I would give all my votes to this if I could. This is Aannoying
The whole workflow performance degrades drastically when you have to resize the dialogs every single time.2022.3.41, Gnome 46
-
NoTuxNoBux
Jul 02, 2024 12:32
For me it's even worse, because this also happens without closing the editor - if I close the project panel, resize it, and then close and reopen it, it's back to its minimal size. I'm on GNOME 46 on Arch right now.
It's especially annoying with the newer 'search all' window because you can't see the results properly without resizing it and the whole point of it is to quickly select results by just using the keyboard.
-
MostHated
Mar 18, 2024 14:36
I have been having this issue as well, it is super annoying. All new windows that I open are set at their minimum possible size, and I have to manually grab corners and make them bigger every time.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This issue appears to be related to a known bug in the GNOME Mutter window manager. Mutter is responsible for managing window states, including size and position. There is already an ongoing issue where Mutter does not correctly store or restore window sizes and positions after they are closed and reopened. This behavior is said to be more prevalent with floating windows and is said to cause them to revert to default states upon restarting.
This problem is not specific to Unity and is a broader issue within the Ubuntu environment under Wayland, affecting a lot of applications. Here is a link to that issue that is currently under investigation by GNOME :[https://gitlab.gnome.org/GNOME/mutter/-/issues/3385
Addressing this issue within Unity would require a significant amount of effort and complexity, which may not be the best use of resources given that the root cause lies outside our control. Hence we are rejecting this bug.