Hello Yao, or anyone else affected,

Accepted mutter into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/46.2-1ubuntu0.24.04.9 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-noble

-- 
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/2111698

Title:
  [SRU] On noble with Intel Arrow Lake systems, glxgears FPS is much
  less than the panel refresh rate

Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Noble:
  Fix Committed
Status in mutter source package in Oracular:
  Won't Fix
Status in mutter source package in Plucky:
  Fix Released
Status in mutter source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

   * When running glxgears fullscreen on Intel Arrow Lake laptop, the
  FPS can be dropped to 2/3 of display refresh rate, which should not
  happen since glxgears has low workload.

  [ Test Plan ]

   * Find a laptop with Intel Arrow Lake CPU and use its integrated GPU

   * Enter Ubuntu Desktop, ensure nothing else is running, open terminal and run
     glxgears -fullscreen

   * The FPS of glxgears reported in the terminal should be close to
  display refresh rate

   * As a regression test, verify that an Intel system *older* than Arrow Lake 
achieves
     glxgears results close to the display refresh rate.

  [ Where problems could occur ]

   * This touches the screen refresh part of mutter in Wayland,
  therefore if this breaks it could affect all systems using GNOME in
  Wayland.

  [ Other Info ]

   * We don't have other issue reported than glxgears e.g. fullscreen
  gaming, however this can be an indicator to actual screen refresh
  issues under such config.

  === Original Report ===

  [Issue]
  Upstream report: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13759

  glxgears -fullscreen does not stick to the refresh rate of the display
  on Arrow Lake systems.

  According to upstream report, applying the following MPs can fix the issue:
  * https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3958
  * https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3999

  I've drafted a debdiff for this issue, but I'd like a review from
  whoever knows the internal workings of KMS.

  [Reproduce Steps]

  Ensure nothing else than terminal is running, then run `glxgears
  -fullscreen` on Intel Arrow Lake with integrated GPU

  [Expected Behavior]

  FPS should be close to the refresh rate of the display.

  [Actual Behavior]

  From the upstream report (with 75 Hz display):

  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  375 frames in 5.0 seconds = 74.992 FPS
  286 frames in 5.0 seconds = 57.136 FPS
  221 frames in 5.0 seconds = 44.151 FPS
  220 frames in 5.0 seconds = 43.953 FPS
  216 frames in 5.0 seconds = 43.157 FPS

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