Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#68088 - [mutter] 3.38 broken refresh rate detection (upstream)
Attached to Project:
Arch Linux
Opened by George (Vash63) - Saturday, 03 October 2020, 13:41 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 05 October 2020, 16:55 GMT
Opened by George (Vash63) - Saturday, 03 October 2020, 13:41 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 05 October 2020, 16:55 GMT
|
DetailsDescription: Gnome 3.38 is unable to detect refresh rates other than 60Hz in X11. This is already being tracked upstream at https://gitlab.gnome.org/GNOME/mutter/-/issues/1430 - I'm reporting here as I'd rather not have my Arch system update while there is a major known regression with 3.38 for my use.
Steps to reproduce: Install mutter 3.38 Observe any window composited by mutter updates at 60Hz causing stuttering issues on other displays |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Monday, 05 October 2020, 16:55 GMT
Reason for closing: Fixed
Additional comments about closing: mutter 3.38.0+40
Monday, 05 October 2020, 16:55 GMT
Reason for closing: Fixed
Additional comments about closing: mutter 3.38.0+40
Comment by freswa (frederik) -
Monday, 05 October 2020, 12:43 GMT
There is an upstream patch available: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1469
Comment by Clément Guérin (geecko) -
Monday, 05 October 2020, 16:32 GMT
Should be fixed as of mutter 3.38.0+40+g209b1ba38-1. This can be closed.