| 2018-04-14 06:47:18 |
Knut Sindre Åbjørsbråten |
bug |
|
|
added bug |
| 2018-04-16 01:41:57 |
Daniel van Vugt |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=781296 |
|
| 2018-04-16 01:41:57 |
Daniel van Vugt |
affects |
wayland (Ubuntu) |
mutter (Ubuntu) |
|
| 2018-04-16 01:42:13 |
Daniel van Vugt |
bug task added |
|
mutter |
|
| 2018-04-16 01:42:21 |
Daniel van Vugt |
mutter (Ubuntu): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2018-04-16 01:42:26 |
Launchpad Janitor |
mutter (Ubuntu): status |
New |
Confirmed |
|
| 2018-04-16 02:21:45 |
Bug Watch Updater |
mutter: status |
Unknown |
Confirmed |
|
| 2018-04-16 02:21:45 |
Bug Watch Updater |
mutter: importance |
Unknown |
Medium |
|
| 2018-05-16 08:18:00 |
Daniel van Vugt |
mutter (Ubuntu): status |
Confirmed |
Triaged |
|
| 2018-05-16 08:18:04 |
Daniel van Vugt |
mutter (Ubuntu): importance |
Undecided |
Medium |
|
| 2018-06-08 13:06:24 |
shankao |
bug |
|
|
added subscriber shankao |
| 2018-06-20 07:52:23 |
Daniel van Vugt |
tags |
amd64 apport-bug artful ubuntu |
amd64 apport-bug artful performance ubuntu |
|
| 2018-06-27 09:56:11 |
Daniel van Vugt |
mutter (Ubuntu): status |
Triaged |
In Progress |
|
| 2018-07-30 23:29:02 |
Alexandre Godard |
bug |
|
|
added subscriber Alexandre Godard |
| 2018-11-09 01:23:16 |
Daniel van Vugt |
summary |
144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS |
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS |
|
| 2018-11-09 01:31:06 |
Daniel van Vugt |
description |
Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. On XOrg it runs higher and feels much smoother. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel.
Using the additional NVidia drivers installed using the Ubuntu software control panel.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libwayland-bin (not installed)
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 14 08:43:29 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301]
InstallationDate: Installed on 2018-03-30 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0610
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 |
Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel.
Using the additional NVidia drivers installed using the Ubuntu software control panel.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libwayland-bin (not installed)
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 14 08:43:29 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301]
InstallationDate: Installed on 2018-03-30 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0610
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 |
|
| 2018-11-12 19:46:49 |
Launchpad Janitor |
mutter (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-11-13 01:20:21 |
Daniel van Vugt |
mutter (Ubuntu): status |
Fix Released |
In Progress |
|
| 2018-11-22 13:48:06 |
Iain Lane |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-11-22 13:48:06 |
Iain Lane |
bug task added |
|
mutter (Ubuntu Cosmic) |
|
| 2018-11-22 13:48:12 |
Iain Lane |
mutter (Ubuntu Cosmic): status |
New |
In Progress |
|
| 2018-11-22 13:48:17 |
Iain Lane |
mutter (Ubuntu Cosmic): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2018-11-23 07:01:17 |
Daniel van Vugt |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-11-23 07:01:24 |
Daniel van Vugt |
mutter (Ubuntu Cosmic): status |
In Progress |
Triaged |
|
| 2018-11-23 07:21:30 |
Daniel van Vugt |
tags |
amd64 apport-bug artful performance ubuntu |
amd64 apport-bug bionic cosmic disco performance ubuntu |
|
| 2018-11-27 09:06:21 |
Daniel van Vugt |
mutter (Ubuntu Cosmic): importance |
Undecided |
Medium |
|
| 2018-11-27 12:18:22 |
dreamcat4 |
bug |
|
|
added subscriber dreamcat4 |
| 2018-11-30 02:02:00 |
Daniel van Vugt |
mutter (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-12-01 03:25:26 |
Justin |
mutter (Ubuntu Cosmic): status |
Triaged |
Fix Released |
|
| 2018-12-03 01:18:19 |
Daniel van Vugt |
mutter (Ubuntu Cosmic): status |
Fix Released |
Triaged |
|
| 2018-12-04 03:53:10 |
Justin |
bug |
|
|
added subscriber Justin |
| 2018-12-25 04:08:46 |
Nana Sakisaka |
bug |
|
|
added subscriber Nana Sakisaka |
| 2019-01-06 21:28:42 |
Eric Karnes |
bug |
|
|
added subscriber Eric Karnes |
| 2019-01-07 00:02:15 |
Bug Watch Updater |
mutter: status |
Confirmed |
Fix Released |
|
| 2019-02-01 09:55:27 |
Daniel van Vugt |
mutter (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-02-22 07:53:02 |
Daniel van Vugt |
bug task added |
|
mutter (Ubuntu Bionic) |
|
| 2019-02-22 07:53:12 |
Daniel van Vugt |
mutter (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-02-22 07:53:15 |
Daniel van Vugt |
mutter (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-02-22 10:01:30 |
Daniel van Vugt |
description |
Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel.
Using the additional NVidia drivers installed using the Ubuntu software control panel.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libwayland-bin (not installed)
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 14 08:43:29 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301]
InstallationDate: Installed on 2018-03-30 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0610
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 |
[Impact]
Gnome Shell redraws at 60Hz 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?
[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. |
|
| 2019-02-22 10:01:50 |
Daniel van Vugt |
description |
[Impact]
Gnome Shell redraws at 60Hz 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?
[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. |
[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?
[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. |
|
| 2019-02-22 10:10:11 |
Daniel van Vugt |
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]
TODO: Use env var to verify?
[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. |
[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.
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. |
|
| 2019-02-22 10:11:50 |
Daniel van Vugt |
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. 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. |
[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.
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. |
|
| 2019-02-22 10:15:45 |
Daniel van Vugt |
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. 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. |
[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.
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. |
|
| 2019-02-22 10:18:02 |
Daniel van Vugt |
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 'glxgears' or some other OpenGL benchmark.
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. |
[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. |
|
| 2019-02-22 10:19:20 |
Daniel van Vugt |
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. |
[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. |
|
| 2019-02-25 09:10:02 |
Daniel van Vugt |
merge proposal linked |
|
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599 |
|
| 2019-02-26 15:02:39 |
Sebastien Bacher |
mutter (Ubuntu Bionic): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2019-02-27 13:32:50 |
Simen Aas Henriksen |
bug |
|
|
added subscriber Simen Aas Henriksen |
| 2019-02-28 10:43:26 |
Marcos Alano |
bug |
|
|
added subscriber Marcos Alano |
| 2019-03-01 11:01:50 |
El jinete sin cabeza |
bug |
|
|
added subscriber El jinete sin cabeza |
| 2019-03-01 14:45:27 |
Timo Aaltonen |
mutter (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-03-01 14:45:30 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-03-01 14:45:31 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2019-03-01 14:45:36 |
Timo Aaltonen |
tags |
amd64 apport-bug bionic cosmic disco performance ubuntu |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-needed verification-needed-cosmic |
|
| 2019-03-05 03:34:35 |
Daniel van Vugt |
tags |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-needed verification-needed-cosmic |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-done verification-done-cosmic |
|
| 2019-03-11 15:00:14 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-03-11 15:00:12 |
Launchpad Janitor |
mutter (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-03-11 19:03:23 |
Nana Sakisaka |
removed subscriber Nana Sakisaka |
|
|
|
| 2019-03-12 09:37:31 |
Daniel van Vugt |
mutter (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2019-03-13 08:09:30 |
Daniel van Vugt |
merge proposal linked |
|
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362 |
|
| 2019-03-13 08:41:40 |
Daniel van Vugt |
bug watch added |
|
https://gitlab.gnome.org/GNOME/mutter/issues/406 |
|
| 2019-03-14 07:15:18 |
Daniel van Vugt |
nominated for series |
|
Ubuntu Disco |
|
| 2019-03-14 07:15:18 |
Daniel van Vugt |
bug task added |
|
mutter (Ubuntu Disco) |
|
| 2019-03-19 02:06:00 |
Daniel van Vugt |
bug watch added |
|
https://gitlab.gnome.org/GNOME/mutter/issues/503 |
|
| 2019-04-30 05:52:50 |
Shane Synan |
bug |
|
|
added subscriber Shane Synan |
| 2019-05-03 17:21:38 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/366676 |
|
| 2019-05-20 07:08:33 |
Daniel van Vugt |
mutter (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-05-28 20:46:22 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-05-28 20:46:31 |
Brian Murray |
tags |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-done verification-done-cosmic |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-done-cosmic verification-needed verification-needed-bionic |
|
| 2019-05-29 03:46:55 |
Daniel van Vugt |
tags |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-done-cosmic verification-needed verification-needed-bionic |
amd64 apport-bug bionic cosmic disco performance ubuntu verification-done verification-done-bionic verification-done-cosmic |
|
| 2019-06-06 09:33:55 |
Launchpad Janitor |
mutter (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-10-23 04:02:22 |
Tyler Alexander Driggers |
mutter (Ubuntu Bionic): assignee |
Daniel van Vugt (vanvugt) |
Tyler Alexander Driggers (exderia) |
|
| 2020-10-23 04:03:44 |
Tyler Alexander Driggers |
mutter (Ubuntu Bionic): assignee |
Tyler Alexander Driggers (exderia) |
|
|
| 2020-10-23 05:59:51 |
Daniel van Vugt |
mutter (Ubuntu Bionic): assignee |
|
Daniel van Vugt (vanvugt) |
|
