Wayland: Mouse cursor becomes resize on the title bar of the render view window. #117583

Closed
opened 2024-01-28 01:12:36 +01:00 by Blender-King · 7 comments

System Information
Operating system: Arch, Wayland, Gnome, fractional scaling, multi monitors with different DPI's.
Graphics card: Arc A770

Blender Version
Broken: 4.1.0 Alpha, 3df7939eec
Worked: 4.0.2, 9be62e85b7

Short description of error
The mouse cursor becomes a resize window so I cannot do things like moving/closing/maximising/minimising the window with the mouse.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

  1. Start Blender
  2. Click Render -> View Render
**System Information** Operating system: Arch, Wayland, Gnome, fractional scaling, multi monitors with different DPI's. Graphics card: Arc A770 **Blender Version** Broken: 4.1.0 Alpha, 3df7939eec96 Worked: 4.0.2, 9be62e85b727 **Short description of error** The mouse cursor becomes a resize window so I cannot do things like moving/closing/maximising/minimising the window with the mouse. **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible). 1. Start Blender 2. Click Render -> View Render
887 KiB
Blender-King added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2024-01-28 01:12:36 +01:00
Member
cc @ideasman42
Pratik Borhade added the
Platform
Linux
Interest
Wayland
labels 2024-01-29 06:17:10 +01:00

Issues relating to libdecor & fractional scaling are largely out of our control.
It's possible fixes related to #109194 caused a change in how the window border is handled.

However it looks the the window borders aren't following the window properly in this example.

  • What version of gnome are you using?
  • What are the scales of each monitor?
Issues relating to libdecor & fractional scaling are largely out of our control. It's possible fixes related to #109194 caused a change in how the window border is handled. However it looks the the window borders aren't following the window properly in this example. - What version of gnome are you using? - What are the scales of each monitor?
Campbell Barton added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-01-30 09:44:45 +01:00
Author
  • Gnome 45.3, libdecor 0.2.2.-1, mutter 45.3-1
  • Monitor 1: 100% (left), Monitor2: right 150% (right, primary).
  1. This does not happen with Blender 4.0.
  2. If I disable Monitor 1, it does not happen with Blender 4.1.
  3. If Monitor 1 is on the right and Monitor 2 is on the left, which is the default position Gnome takes, but different from the physical position, it does not happen with Blender 4.1. That is, physically M1 is on the left and M2 is on the right, but whenever I disable/enable monitors in Gnome Settings, it becomes M2 on the left and M1 on the right, probably because of the port order of the GPU.
* Gnome 45.3, libdecor 0.2.2.-1, mutter 45.3-1 * Monitor 1: 100% (left), Monitor2: right 150% (right, primary). 1. This does not happen with Blender 4.0. 2. If I disable Monitor 1, it does not happen with Blender 4.1. 3. If Monitor 1 is on the right and Monitor 2 is on the left, which is the default position Gnome takes, but different from the physical position, it does not happen with Blender 4.1. That is, physically M1 is on the left and M2 is on the right, but whenever I disable/enable monitors in Gnome Settings, it becomes M2 on the left and M1 on the right, probably because of the port order of the GPU.

Recently I ran into this bug:

  • This isn't related to fractional-scaling (occurs without any fractional scaling).

  • This seem to occur with new windows that are larger than the display size, whos size is clamped after creation.

    This command causes the error:

    blender --factory-startup -p 0 0 2060 3680 -w

    But this command doesn't:

    blender --factory-startup -p 0 0 1060 2680 -w

This needs further investigation.

Recently I ran into this bug: - This isn't related to fractional-scaling (occurs without any fractional scaling). - This seem to occur with new windows that are larger than the display size, whos size is clamped after creation. This command causes the error: `blender --factory-startup -p 0 0 2060 3680 -w` But this command doesn't: `blender --factory-startup -p 0 0 1060 2680 -w` This needs further investigation.
Author

When Blender first starts, its position sort-of appears to be at the (0,0) of the virtual space that combines the two monitors, and then it moves to the last window position (the blue rectangles represents monitors). I think Blender is not the only application that showed this kind of weird behaviour when fractional scaling and custom monitor positions (meaning that the positions different from the default positions that Gnome sets up when the monitors are first connected) are used.

image

When Blender first starts, its position sort-of appears to be at the (0,0) of the virtual space that combines the two monitors, and then it moves to the last window position (the blue rectangles represents monitors). I think Blender is not the only application that showed this kind of weird behaviour when fractional scaling and custom monitor positions (meaning that the positions different from the default positions that Gnome sets up when the monitors are first connected) are used. ![image](/attachments/e3d5d06f-d885-40a9-8661-79bb6c709722)
9.2 KiB
Campbell Barton added
Priority
High
and removed
Priority
Normal
labels 2024-02-28 04:43:59 +01:00

Setting high priority as the title bar completely unusable when this bug occurs.

Setting high priority as the title bar completely unusable when this bug occurs.
Blender Bot added
Status
Resolved
and removed
Status
Needs Information from User
labels 2024-02-28 06:12:32 +01:00
Author

It no longer happens with 5f70bd0e46, but each time I open the render window, I can see that it starts at the centre of the left monitor (secondary), gets enlarged to fill the left monitor, and then move to the right monitor (primary) and becomes a child window. Also, when the render view window opens/closes, if the viewport of Blender is render view mode, I can see it gets redrawn (denoising working again). These are not serious problems, but just in case you did not know.

It no longer happens with 5f70bd0e46bd, but each time I open the render window, I can see that it starts at the centre of the left monitor (secondary), gets enlarged to fill the left monitor, and then move to the right monitor (primary) and becomes a child window. Also, when the render view window opens/closes, if the viewport of Blender is render view mode, I can see it gets redrawn (denoising working again). These are not serious problems, but just in case you did not know.
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#117583
No description provided.