** Description changed: [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] - TODO: Use env var to verify? + 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. Move the window around in rapid circles for 10 seconds or so. + + 5. Verify it shows high FPS values closer to the hardware spec than 60. + + 6. If you are unsure of the result, try again using a USB mouse instead + of the touchpad so as to ensure your input is also at a high rate (some + laptops have slow touchpads but it generally should not be a problem on + laptops with high refresh rate displays). [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.
** Description changed: [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 + CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: - journalctl -f | grep FPS + journalctl -f | grep FPS 4. Move the window around in rapid circles for 10 seconds or so. 5. Verify it shows high FPS values closer to the hardware spec than 60. 6. If you are unsure of the result, try again using a USB mouse instead of the touchpad so as to ensure your input is also at a high rate (some laptops have slow touchpads but it generally should not be a problem on laptops with high refresh rate displays). + 7. If you are still unsure of the result, replace step 4 with simply + running 'glxgears' or similar. + [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. ** Description changed: [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. Move the window around in rapid circles for 10 seconds or so. + 4. In a new window run 'glxgears' or some other OpenGL benchmark. - 5. Verify it shows high FPS values closer to the hardware spec than 60. - - 6. If you are unsure of the result, try again using a USB mouse instead - of the touchpad so as to ensure your input is also at a high rate (some - laptops have slow touchpads but it generally should not be a problem on - laptops with high refresh rate displays). - - 7. If you are still unsure of the result, replace step 4 with simply - running 'glxgears' or similar. + 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. ** Description changed: [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 'glxgears' or some other OpenGL benchmark. + 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. ** Description changed: [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. + mutter 3.32 to mutter 3.30. If regressions did occur they would be + visible in the frame rate of the entire screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
