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 <daniel.van.v...@canonical.com>  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/2038801

Title:
  Secondary GPU frame rates are held back by dynamic-max-render-time

Status in Mutter:
  Fix Released
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 ]

  Secondary GPU frame rates are held back by dynamic-max-render-time as
  shown on this amdgpu setup connected to a 60 Hz monitor:

  main: 30 FPS
  main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS

  https://gitlab.gnome.org/GNOME/mutter/-/issues/3070

  [ Test Plan ]

  This is imprecise because many machines won't exhibit a measurable
  difference...

  1. Set up a dual GPU machine with dual monitors using an open source
  driver such as amdgpu or nouveau. If you are using Mutter 46 or later
  then the closed source Nvidia driver may also be used in theory.

  2. In a Wayland session, check that the frame rate being achieved on
  the monitor connected to the secondary GPU is at least that of the
  refresh rate.

  3. Add CLUTTER_PAINT=disable-dynamic-max-render-time to
  /etc/environment and reboot.

  4. In a Wayland session, check that the frame rate on the monitor
  connected to the secondary GPU has not changed (didn't get better)
  after the environment change.

  5. Remove the change from /etc/environment.

  [ Where problems could occur ]

  Anywhere in frame scheduling and frame rate performance, since that is
  what changed.

  [ Other Info ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2038801/+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

Reply via email to