Hi Chris / Alessandro,
I'm possibly doing something wrong, but I was trying to upgrade to
mutter 46.2-1ubuntu0.24.04.6 from -proposed to help with this bug
verification, and this is what I noticed.
I have the following packages installed:
fa...@fabiomirmar.net@noble-desktop:~$ sudo dpkg -l | grep mutter
ii gir1.2-mutter-14:amd64 46.2-1ubuntu0.24.04.5
amd64 GObject introspection data for Mutter
ii libmutter-14-0:amd64 46.2-1ubuntu0.24.04.5
amd64 window manager library from the Mutter window manager
ii mutter-common 46.2-1ubuntu0.24.04.6
all shared files for the Mutter window manager
ii mutter-common-bin 46.2-1ubuntu0.24.04.5
amd64 shared programs for the Mutter window manager
fa...@fabiomirmar.net@noble-desktop:~$
I've been able to upgrade mutter-common to 46.2-1ubuntu0.24.04.6, but
gir1.2-mutter-14:amd64 depends on libmutter-14-0:amd64, that depends on
mutter-common-bin. And this is what I see when I try to upgrade mutter-
common-bin:
fa...@fabiomirmar.net@noble-desktop:~$ sudo apt-get --only-upgrade install
mutter-common-bin=46.2-1ubuntu0.24.04.6
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
evolution-data-server evolution-data-server-common gir1.2-accountsservice-1.0
gir1.2-gck-2 gir1.2-gcr-4 gir1.2-gdm-1.0 gir1.2-geoclue-2.0
gir1.2-gnomeautoar-0.1 gir1.2-gnomebg-4.0
gir1.2-gnomebluetooth-3.0 gir1.2-gnomedesktop-3.0 gir1.2-gweather-4.0
gir1.2-javascriptcoregtk-6.0 gir1.2-nm-1.0 gir1.2-nma4-1.0 gir1.2-polkit-1.0
gir1.2-rsvg-2.0
gir1.2-upowerglib-1.0 gir1.2-webkit-6.0 gkbd-capplet gnome-shell-common
gstreamer1.0-pipewire libabsl20220623t64 libcamel-1.2-64t64
libebackend-1.2-11t64 libebook-1.2-21t64
libebook-contacts-1.2-4t64 libecal-2.0-3 libedata-book-1.2-27t64
libedata-cal-2.0-2t64 libedataserver-1.2-27t64 libedataserverui-1.2-4t64 libei1
libeis1 libfreerdp-server3-3
libfreerdp3-3 libgnomekbd-common libgnomekbd8 libllvm17t64 libphonenumber8
libprotobuf32t64 libtss2-tcti-libtpms0t64 libtss2-tcti-spi-helper0t64
libtss2-tctildr0t64 libwinpr3-3
libxcb-res0 libxklavier16 linux-headers-6.8.0-49
linux-headers-6.8.0-49-generic linux-image-6.8.0-49-generic
linux-modules-6.8.0-49-generic linux-modules-extra-6.8.0-49-generic
linux-tools-6.8.0-49 linux-tools-6.8.0-49-generic mutter-common
python3-netifaces switcheroo-control xwayland
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
notification-daemon policykit-1-gnome
The following packages will be REMOVED:
gdm3 gir1.2-mutter-14 gnome-remote-desktop gnome-shell
gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons-ng
gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-tiling-assistant libmutter-14-0
ubuntu-desktop-minimal ubuntu-session
The following NEW packages will be installed:
notification-daemon policykit-1-gnome
The following packages will be upgraded:
mutter-common-bin
1 upgraded, 2 newly installed, 11 to remove and 4 not upgraded.
Need to get 128 kB of archives.
After this operation, 16.5 MB disk space will be freed.
Do you want to continue? [Y/n] n
So, it would try to remove gdm3, ubuntu-desktop-minimal, among others.
Is that right, or am I missing something?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2080698
Title:
Dragging a window can cause full framebuffer damage
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Noble:
Fix Committed
Status in mutter source package in Oracular:
Fix Released
Bug description:
[ Impact ]
Window movements can cause a re-draw of the whole screen.
That causes an unnecessary performance hit, especially noticeable when using
a remote session.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/3630
Upstream fix:
https://gitlab.gnome.org/GNOME/mutter/-/commit/030270ba3bf14b23a2d7a5371cf158ff2591f327
[ Test Plan ]
1. Set up an Ubuntu system and log in
2. Launch the Looking Glass debugger by pressing `Alt+F2`, typing `lg`, and
pressing Enter
3. Navigate to the "Flags" tab in the top right corner of the debug window
4. Scroll down and enable the `PAINT_DAMAGE_REGION` flag. By enabling this
flag, a red overlay will appear to show regions where the screen is being
redrawn and helps visualize framebuffer damage.
6. Drag a window across the screen
7. Verify that the red overlay only covers the window rectangle rather than
the whole screen
On the first drag the bug is expected to still be reproducible, but
all subsequent drags should not trigger the bug.
[ Where problems could occur ]
mutter is the Wayland compositor library that provides graphics and inputs
for the GNOME desktop, thus is a critical component.
Problems could manifest with the action of dragging a window not working
anymore, or sudden log-out if gnome-shell crashes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2080698/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
