Window size is broken in Linux Gnome Wayland #117863

Open
opened 2024-02-05 18:26:35 +01:00 by Max Mustermann · 12 comments

System Information
Operating system: Fedora Linux (Wayland Gnome 45.3)
Graphics card: AMD

Blender Version
Broken: really broken in 3.6.5 (e2b5e831) until 4.0.2 (current version), some visual bugs since at least 3.3.0
Something changed in 3.6.5 (ed38ca98g), the bug only happens when maximizing there, not when un-maximizing. Although when the window is grabbed from a maximized state it is the wrong size there too, but it resizes correctly as soon as it refreshes.
Worked: ?

Short description of error
Sometimes a Blender window is the wrong size

Exact steps for others to reproduce the error
Un-maximize and maximize a Blender window a few times.

**System Information** Operating system: Fedora Linux (Wayland Gnome 45.3) Graphics card: AMD **Blender Version** Broken: really broken in 3.6.5 (e2b5e831) until 4.0.2 (current version), some visual bugs since at least 3.3.0 Something changed in 3.6.5 (ed38ca98g), the bug only happens when maximizing there, not when un-maximizing. Although when the window is grabbed from a maximized state it is the wrong size there too, but it resizes correctly as soon as it refreshes. Worked: ? **Short description of error** Sometimes a Blender window is the wrong size **Exact steps for others to reproduce the error** Un-maximize and maximize a Blender window a few times.
Max Mustermann added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2024-02-05 18:26:36 +01:00
Iliya Katushenock added the
Interest
Wayland
Platform
Linux
labels 2024-02-05 18:30:46 +01:00
Author

This happens without any fractional scaling on GNOME 45.3, so it might not be related to #109194.

This happens without any fractional scaling on GNOME 45.3, so it might not be related to #109194.
Author

Window snapping triggers the bug very reliably. The video is not edited.

Window snapping triggers the bug very reliably. The video is not edited.

@max-mustermann could you please test with a recent daily build of 4.1?

There have been multiple fixes to LIBDECOR's window size logic since 3.6, so the issue reported here may be resolved.

Related fixes for reference:

@max-mustermann could you please test with a recent daily build of 4.1? There have been multiple fixes to LIBDECOR's window size logic since 3.6, so the issue reported here may be resolved. Related fixes for reference: - 004420af8ffa22846ce46faf7d33208e19417c24 - f845a3992cff5f660b2f94b31ab609f10e1e6b6c - 1455315111ae769d101413fe600662484ff46d62 - 39f378da37eedb918a69a31c68c34e5a9263754c - ba33dba2b6aa5514ac0cc8359e3561ffdefbbeb0 - dcaeed752237a8e31cb12351aef1c5a7348c9c32
Campbell Barton added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-02-28 10:04:07 +01:00
Author

I have tested a daily build of 4.1 and 4.2 and most bugs shown in my window snapping video still persist in both.

I have tested a daily build of 4.1 and 4.2 and most bugs shown in my window snapping video still persist in both.

@max-mustermann for this report to be useful we need to know which bugs remain.

@max-mustermann for this report to be useful we need to know which bugs remain.
Author

They mostly involve a second window.

1:
Have both windows snapped to a side.
Grab the second window.
The second window will look like this sometimes until it refreshes.
Blender03.png Blender04.png
Blender06.png

When maximizing before it refreshes, it looks like this:
Blender08.png
Blender09.png
Blender10.png

2:
Have both windows snapped to a side.
Grab a window to "unsnap" it.
The other window will shrink in size sometimes.
This is permanent until the other window is resized.
Blender02.png

Edit: Found a more consistent way to trigger Bug 2:

Open Blender (and click to get rid of the splash screen).
Snap the window to a side.
Press F11 to open the Blender Render window.
Move the Blender Render window using SUPER+LMB to snap the Blender Render window to the other side.
Unsnap the main window.
The Blender Render window will shrink in size too.
And I get a Gnome notification that Blender crashed with a segfault but I don't notice anything crashing and there is no output in the console about a crash.

They mostly involve a second window. **1:** Have both windows snapped to a side. Grab the second window. The second window will look like this sometimes until it refreshes. ![Blender03.png](/attachments/4fa3fed2-7873-480f-bab7-866d42967556) ![Blender04.png](/attachments/414bbd14-8df0-41b8-a02c-7e2eb4aed075) ![Blender06.png](/attachments/77c8ecd4-dc23-45a0-bdeb-cb99a5841838) When maximizing before it refreshes, it looks like this: ![Blender08.png](/attachments/1e2d26f1-dedc-4234-b104-923e7244b728) ![Blender09.png](/attachments/7b80f01c-750a-45b6-b4b8-2b585e7317e8) ![Blender10.png](/attachments/cf0fee77-de0a-4bb6-aa5f-b5745c421dc3) **2:** Have both windows snapped to a side. Grab a window to "unsnap" it. The other window will shrink in size sometimes. This is permanent until the other window is resized. ![Blender02.png](/attachments/037d0f51-5d16-4b55-b954-6f2c44fc821a) Edit: Found a more consistent way to trigger Bug 2: Open Blender (and click to get rid of the splash screen). Snap the window to a side. Press F11 to open the Blender Render window. Move the Blender Render window using SUPER+LMB to snap the Blender Render window to the other side. Unsnap the main window. The Blender Render window will shrink in size too. And I get a Gnome notification that Blender crashed with a segfault but I don't notice anything crashing and there is no output in the console about a crash.
Author

Maybe this is related, but repeatedly opening and closing the Blender Render window (F11, then closing the window with X) gave me this error in the console:
Blender12.png

After that error was triggered, version 4.0.2 would not be able to open a new Blender Render window, but other windows like Blender Preferences would still open.
In the most recent 4.2 daily however, Blender becomes completely unresponsive to all inputs as soon as the bug is triggered. So this is a regression within the bug? Do I open a new report for this?

Maybe this is related, but repeatedly opening and closing the Blender Render window (F11, then closing the window with X) gave me this error in the console: ![Blender12.png](/attachments/13d6e209-47fe-4bd9-b78a-bc98627974d4) After that error was triggered, version 4.0.2 would not be able to open a new Blender Render window, but other windows like Blender Preferences would still open. In the most recent 4.2 daily however, Blender becomes completely unresponsive to all inputs as soon as the bug is triggered. So this is a regression within the bug? Do I open a new report for this?
Author

Repeatedly toggling window fullscreen with Window -> Toggle Window Fullscreen makes the window extend beyond the screen on the bottom after the second cycle.

Edit: Seems to be fixed in the recent daylies.

Repeatedly toggling window fullscreen with Window -> Toggle Window Fullscreen makes the window extend beyond the screen on the bottom after the second cycle. Edit: Seems to be fixed in the recent daylies.
Member

Grab the second window.
The second window will look like this sometimes until it refreshes.

Maybe fixed by e078112a53 ?

> Grab the second window. The second window will look like this sometimes until it refreshes. Maybe fixed by e078112a535b0f51476edcaf0563d7583a2d6ac4 ?
Author

Maybe fixed by e078112a53 ?

Sadly it still happens in the recent daily, but I can't trigger the following bug in the recent daily anymore:

Repeatedly toggling window fullscreen with Window -> Toggle Window Fullscreen makes the window extend beyond the screen on the bottom after the second cycle.

> Maybe fixed by e078112a53 ? Sadly it still happens in the recent daily, but I can't trigger the following bug in the recent daily anymore: > Repeatedly toggling window fullscreen with Window -> Toggle Window Fullscreen makes the window extend beyond the screen on the bottom after the second cycle.
Author

I found a more consistent way to trigger Bug 2. I updated the comment about it.

Edit: Found a more consistent way to trigger Bug 2

I found a more consistent way to trigger Bug 2. I updated the comment about it. > Edit: Found a more consistent way to trigger Bug 2
Pratik Borhade added
Status
Needs Triage
and removed
Status
Needs Information from User
labels 2024-03-29 03:41:26 +01:00
Author

Blender 4.1.1:
When starting out with a maximized window and then unmaximizing it, Blender becomes unresponsive to all inputs until the window focus has been switched away and back to Blender again. This only happens the first time after Blender has been started.
It seems related to window sizes so I'm putting it here.

Blender 4.1.1: When starting out with a maximized window and then unmaximizing it, Blender becomes unresponsive to all inputs until the window focus has been switched away and back to Blender again. This only happens the first time after Blender has been started. It seems related to window sizes so I'm putting it here.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#117863
No description provided.