Workaround:
1. Add a line to /etc/environment like:
CLUTTER_DEFAULT_FPS=144
or whatever your monitor's real refresh rate is.
2. Reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but Wayland sessions seem to c
** Tags added: performance
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but Wayland sessions seem to cap rendering at
60FPS
To manage notific
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/176
** Changed in: mutter
Status: Unknown => Confirmed
** Changed in: mutter
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/176
Thanks for the bug report. It's been a known issue for a while:
https://bugzilla.gnome.org/show_bug.cgi?id=781296
** Bug watch added: GNOME Bug Tracker #781296
https://bugzilla.gnome.org/show_bug.cgi?id=781296
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Also affects: mutter via
