Resizing XWayland & X11 windows is extremely slow

Bug #2107245 reported by Alexander Koskovich
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Unknown
Mutter
New
Unknown
gtk4 (Ubuntu)
Status tracked in Questing
Plucky
In Progress
Medium
Alessandro Astone
Questing
Fix Committed
Medium
Unassigned
mutter (Ubuntu)
Status tracked in Questing
Plucky
Opinion
Undecided
Unassigned
Questing
Opinion
Undecided
Unassigned

Bug Description

[ Impact ]

When resizing X11 windows that use server-size-decorations on Xorg or through XWayland (Discord, Spotify, etc) the resize does not take effect until seconds after holding the resize. If you let go of the resize before it happens then window does not resize at all.

[ Test Plan A ]

1. Enable fractional scaling and set a scaling factor of 125% or 150%
2. Log into an Ubuntu Desktop Wayland session
3. Start Spotify
4. Try to resize the window
5. Verify that the window can be resized normally

[ Test Plan B ]

1. Enable fractional scaling and set a scaling factor of 125% or 150%
2. Log into an Ubuntu Desktop Xorg session
3. Start Spotify
4. Try to resize the window
5. Verify that the window can be resized normally

[ Where problems could occur ]

This update is included in the 4.18.5 bugfix release from upstream. See bug 2109964

[ Other info ]

The issue was originally reported on NVIDIA hardware:
"""
Ubuntu 25.04 Beta
NVIDIA RTX 5090 (570.133.07)
"""
but it can be reproduced on any graphics driver.

Revision history for this message
Alexander Koskovich (nexusprism) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2107245/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
summary: - Resizing XWayland windows w/NVIDIA is extremely slow
+ Resizing XWayland & X11 windows w/NVIDIA is extremely slow
Revision history for this message
Alessandro Astone (aleasto) wrote (last edit ): Re: Resizing XWayland & X11 windows w/NVIDIA is extremely slow

I can reproduce on non-NVIDIA.
Do you use fractional scaling by any chance?

> XWayland & X11 windows
What does that mean exactly? You can reproduce by resizing any window on an Xorg session?

affects: xorg (Ubuntu) → mutter (Ubuntu)
no longer affects: ubuntu
Revision history for this message
Alexander Koskovich (nexusprism) wrote :

> Do you use fractional scaling by any chance?
Yes, 150%

> You can reproduce by resizing any window on an Xorg session?
Did some further testing, and I can't reproduce the issue with apps like Chrome or Ptyxis, but I can with Discord, Telegram, and Spotify. Only when they are inside an Xorg session or running under XWayland, if I force them to run as Wayland they are fine.

I turned off fractional scaling, and resizing is fine.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you open a Terminal window and leave 'top' running before reproducing the bug? I'm wondering if any process (like mutter-x11-frames, gnome-shell or the app itself) is requiring too much CPU.

tags: added: nvidia performance
Changed in mutter (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
summary: - Resizing XWayland & X11 windows w/NVIDIA is extremely slow
+ Resizing XWayland & X11 windows is extremely slow
Changed in mutter (Ubuntu):
milestone: none → plucky-updates
tags: added: fixed-in-gtk-4.18.5 fixed-upstream
Changed in gtk4 (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
milestone: none → plucky-updates
Changed in gtk:
status: Unknown → Fix Released
Changed in mutter:
status: Unknown → New
Revision history for this message
Alexander Koskovich (nexusprism) wrote :

Is it possible to patch the GTK package to include https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/8459 while we wait for a new GTK release to come out?

Changed in mutter (Ubuntu):
status: Confirmed → Opinion
milestone: plucky-updates → none
Changed in mutter (Ubuntu Plucky):
status: New → Opinion
Changed in gtk4 (Ubuntu Questing):
milestone: plucky-updates → ubuntu-25.10
Changed in gtk4 (Ubuntu Plucky):
milestone: none → plucky-updates
importance: Undecided → Medium
status: New → Triaged
tags: added: desktop-needs-sru
Revision history for this message
Alessandro Astone (aleasto) wrote :

I can confirm that https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/8459 fixes the issue for me

description: updated
Changed in gtk4 (Ubuntu Questing):
status: Triaged → In Progress
Changed in gtk4 (Ubuntu Plucky):
status: Triaged → In Progress
assignee: nobody → Alessandro Astone (aleasto)
Changed in gtk4 (Ubuntu Questing):
assignee: nobody → Alessandro Astone (aleasto)
status: In Progress → Fix Committed
assignee: Alessandro Astone (aleasto) → nobody
Revision history for this message
zz luz (myth5) wrote (last edit ):

sorry,i make a mistake.i don't know why i can change this status.

Changed in gtk4 (Ubuntu Plucky):
status: In Progress → Fix Released
zz luz (myth5)
information type: Public → Public Security
Changed in gtk4 (Ubuntu Plucky):
status: Fix Released → In Progress
information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.