Hello Knut, or anyone else affected,

Accepted mutter into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.30.2-1~ubuntu18.10.4 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 and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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.

** Changed in: mutter (Ubuntu Cosmic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Triaged
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Gnome Shell redraws at 60 FPS at most, regardless of the hardware
  refresh rate, and regardless of the current display mode. This is
  particularly annoying for owners of 144Hz/120Hz/240Hz displays.

  [Test Case]

  0. Find a monitor or laptop with a high refresh rate (120Hz or more),
  noting NOT to trust gnome-control-center or xrandr because an
  unrelated bug in mutter may cause those to report 120Hz even on 60Hz
  displays. Make sure the advertised hardware specs show the display is
  a high frame rate.

  1. Edit /etc/environment and add:
     CLUTTER_SHOW_FPS=1

  2. Reboot.

  3. Open a terminal window and run:
     journalctl -f | grep FPS

  4. In a new window run 'glmark2' or some other OpenGL benchmark that
  is not frame rate limited (note: glxgears for unrelated reasons IS
  frame rate limited in Wayland sessions, but can be used in Xorg
  sessions).

  5. Verify the terminal window from step 4 shows high FPS values coming
  from the journalctl log that match the hardware spec, and are much
  higher than 60.

  [Regression Potential]

  Medium to low. This patch has been used upstream and in Ubuntu 19.04
  for some months already without any issues. Although minor syntactical
  changes had to be made to avoid conflicts when backporting it from
  mutter 3.32 to mutter 3.30. If regressions did occur they would be
  visible in the frame rate of the entire screen.

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