This bug was fixed in the package mutter - 46.2-1ubuntu0.24.04.1
---------------
mutter (46.2-1ubuntu0.24.04.1) noble; urgency=medium
[ Daniel van Vugt ]
* New upstream release 46.2 (LP: #2068598)
- Fixed mouse clicks falling through to the window behind (LP: #2026194)
- Fixed a crash in meta_wayland_transaction_commit (LP: #2061739)
- Fixed night light getting stuck on (LP: #2066902)
* New upstream release 46.1 (LP: #2064735):
- Fixed blank screen on hybrid GPU machines using nouveau (LP: #2066931)
- Fixed a monitor hotplug crash (LP: #2050865)
- Improved performance on secondary GPU monitors (LP: #2038801)
* Refreshed patches:
- Support-Dynamic-triple-double-buffering.patch (LP: #2070437, LP: #2070438)
- meson-Do-not-mark-CI-test-tools-as-required.patch
- Mark-several-additional-tests-as-flaky.patch
* Add clutter/conform gesture tests to the list of known flaky ones:
it's a new test in Mutter 46 and not yet reliable.
* Add build-Compile-schemas-locally-for-use-in-build-tests.patch to compile
gsettings schemas for use in build tests. Debian CI requires this now and
it makes rebuilds more resilient against infrastructure changes.
* Add wayland-Disable-linux-drm-syncobj-v1.patch to avoid enabling major
new features in Noble updates, as detailed in:
https://lists.ubuntu.com/archives/ubuntu-release/2024-May/006087.html
* Add backends-Handle-null-views-instead-of-creating-dummy-view.patch
to prevent "clutter_frame_clock_notify_presented: code should not be
reached" log spam in some Nvidia Wayland sessions (LP: #1967707)
* Add backends-Restore-support-for-X11-cursor-themes.patch to restore
support for X11 cursor themes, which was lost in Mutter 46.0
(LP: #2062377, LP: #2063869)
[ Jeremy Bícha ]
* Stop compiling gsettings schemas in debian/rules
* Opt into Salsa CI
* Drop packaging references to Hurd since this is Linux-only
* Update libmutter-14-0.symbols
* Update Breaks
* Refreshed patches:
- window-Add-ability-to-override-the-edge-constraints.patch
- x11-Add-support-for-fractional-scaling-using-Randr.patch
* Drop upstreamed patches:
- Nvidia-secondary-GPU-copy-acceleration.patch
- compositor-sync-ring-Allow-the-gpu_fence-to-be-moved.patch
[ Marco Trevisan ]
* Add place-Always-center-initial-setup.patch (LP: #2016013)
-- Daniel van Vugt <[email protected]> Fri, 28 Jun 2024
17:35:12 +0800
** Changed in: mutter (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/2070438
Title:
Fullscreen direct scanout is not used if you enable the hidden
experimental VRR feature in Mutter 46
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Noble:
Fix Released
Status in mutter source package in Oracular:
Fix Released
Bug description:
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden
experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set CLUTTER_PAINT=damage-region in /etc/environment
2. gsettings set org.gnome.mutter experimental-features
'["variable-refresh-rate"]'
3. Reboot.
4. Log into a Wayland session.
5. Don't panic. The screen is meant to turn red whenever something changes.
6. In Settings > Display verify that variable refresh rate is detected and
enabled.
7. Open Google Chrome (Firefox won't work) and start an animation like
https://www.vsynctester.com/
8. Press F11 to make it full screen.
9. Verify the screen has now stopped being red.
10. Press F11 again to exit full screen.
11. Verify the screen has gone red again.
If the screen went black at the end, don't panic. That's a separate
bug 2066080.
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple
buffering or stay double buffering, the main risk is that triple
buffering wouldn't be used in some situation where we would rather
have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is
still buggy (bug 2066080)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2070438/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
