These two bugs have been there for years. After months not using Unity I would have thought they were fixed…
It’s the same problem I reported here: in 2021.2.0a16 - Ubuntu based Linux - Editor doesn't start maximized ...
I received an answer about this bug from the bug report portal saying:
Your bug report status has changed to Closed with the resolution Duplicate.
The original issue was closed with resolution Third Party Issue.
Resolution Notes: 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 :[[46] xwayland: SSD Windows don't remember maximized state (#3385) · Issues · GNOME / mutter · GitLab
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.
Okay then… 
I may have found a workaround:
In “~/your_project_name/UserSettings/Layouts/default-6000.dwlt”, lines:
m_PixelRect:
serializedVersion: 2
x: 0
y: 24
width: 1920
height: 1016
m_ShowMode: 4
m_Title: Tile Palette
m_RootView: {fileID: 11}
m_MinSize: {x: 875, y: 300}
m_MaxSize: {x: 10000, y: 10000}
m_Maximized: 1
change the line:
m_MinSize: {x: 875, y: 300}
to:
m_MinSize: {x: 1920, y: 1048}
(y: 1080 is too large, the status bar disappears.)
Hopefully, it’s going to last. 
width: 1920
height: 1016
changing them lasts only one time.
Bug report closed because:
Hello.
So I will be closing this ticket because of the same reason as the first one: using unsupported environment.
Like I mentioned before, while using Ubuntu 24.04 I did not manage to get the same issue as showcased in your picture.
If you have any questions, feel free to reply here.
Best regards,
Customer QA Team
This will be my last bug report then. Oh well.
I had an incident with this fix where, for some reason the
m_MinSize: {x: 1916, y: 1048}
line had reversed to the default size. I thought that this workaround wouldn’t hold but I decided to give it another try and this time it does hold.
The correct minimum size though is:
m_MinSize: {x: 1916, y: 1040}
Problem fixed then, if not solved.
Call me obsessed… I managed and fixed this problem by switching from the XFCE window manager to Metacity:
Looks better doesn’t it? 
@jonabali Now Metacity is a gnome thing, does that mean that now my bug reports will be acknowledged or will they be rejected because it was the window manager for Gnome 2 and the current version is Gnome 3?
Hey, APSchmidt! Unfortunately, they will not, as we only support GNOME 3 issues with Mutter. Sorry to be the bearer of the bad news, but I’m glad to hear that you at least found a workaround for this.
Thanks anyway! 
At least the situation is clear. Using Linux, I’m somehow used to workarounds. Since I found one for the editor window geometry and the start image, I’m glad. 
I have a question though: where can we put requests to the team? Like the one mentioned here: Camera preview not showing when I select my camera, bad idea!
Thank you!
Currently, the only way to pass feature requests is here.
All right, I tried Gnome 3. Beside the problems I experienced in XFCE and I reported here, there was one I didn’t mention: preferences are not saved. I tried countless times in two different projects, no way. New colour palette does not apply to the editor and in Scene the setting “Create new objects centered” do not hold. I tried Gnome 3 in case it would fix this; it doesn’t.
I’m back to xfwm4, XFCE window manager then since the only thing I get right is the start image; I can live without it.
Hopefully, preferences do not holding is not project wrecking because I will not set them each time I launch a project.
End of story. Maybe I’ll use Ubuntu once, after I bought myself a new computer.
Well, no. I wasted my day on this, installed Ubuntu 20.04, installed Unity Hub, installed VS Code etc. created a new project to test the result:
And, this is how it looks…
So, Ubuntu works better than Linux Mint? Really? I’ve wasted hours and a huge amount of internet data, 9.21 Gb, for nothing!
I wanted to try, I tried. I won’t do it again.
Hello again! Red scene view is usually related to GPU drivers. Typically, this bug occurs when the Editor is launched with an Intel iGPU. I can see that you have a GTX 970, so it’s possible that Ubuntu is simply not selecting your GPU as the default one. We only support Unity launched with AMD and NVIDIA GPUs. Regarding the preferences, it would’ve been great to get your Editor.log to debug this more thoroughly, but I would expect that you don’t have Ubuntu installed anymore. However, if you still do, and are still facing any of these issues, please report this via the Bug Reporter so your log files are attached. We’ll then take a further look into this!
