Bug 1883303

Summary: [RHEL-8] Cannot set refresh rate for displays on Wayland
Product: Red Hat Enterprise Linux 8 Reporter: solo24 <antonovitch>
Component: mutterAssignee: Jonas Ådahl <jadahl>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: antonovitch, bstinson, carl, fmuellner, jwboyer
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-28 07:30:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The system messages log file
none
The output for Mutter.DisplayConfig
none
The output for Mutter.DisplayConfig
none
The output for Mutter.DisplayConfig and modetest
none
The patch for meta_calculate_drm_mode_refresh_rate. none

Description solo24 2020-09-28 17:09:51 UTC 
Created attachment 1717302 [details]
The system messages log file

Description of problem:
When start a Gnome Wayland session, and from the gnome-control-center cannot set refresh rate for displays.


Version-Release number of selected component (if applicable):
NAME="Red Hat Enterprise Linux"
VERSION="8.3 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.3"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.3 Beta (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8.3:beta"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.3 Beta"

gnome-session-wayland-session-3.28.1-8.el8.x86_64
mutter-3.32.2-36.el8.x86_64

How reproducible:
100% reproducible in all attempts

Steps to Reproduce:
1. Log into a Gnome Wayland session
2. Use the gnome-control-center interface
3. Open Decices > Displays > Refresh rate (59.98 Hz)
4. Apply

Actual results:
When push the button Apply on screen, display is black during 20 sec and return back to the previous settings Refresh Rate.

Expected results:
When push the button Apply on screen, the pop-up menu appear for 20 sec on the screen and user can confirm display settings keep or revert. The new refresh rate in use.

Additional info:
This same bug was found in the release RHEL 8.2 as well.
Comment 1 Jonas Ådahl 2020-09-30 08:48:52 UTC 
Can you run the following three commands

gdbus call -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetResources > mutter-display-resources.txt

gdbus call -e -d org.gnome.Mutter.DisplayConfig -o /org/gnome/Mutter/DisplayConfig -m org.gnome.Mutter.DisplayConfig.GetCurrentState > mutter-display-state.txt

modetest > modetest.txt

and attach the resulting files here?
Comment 3 solo24 2020-09-30 16:13:35 UTC 
Created attachment 1717931 [details]
The output for Mutter.DisplayConfig
Comment 4 solo24 2020-09-30 16:14:03 UTC 
Created attachment 1717932 [details]
The output for Mutter.DisplayConfig
Comment 5 solo24 2020-09-30 16:14:52 UTC 
Created attachment 1717933 [details]
The output for Mutter.DisplayConfig and modetest

Please see the attached files for Mutter.DisplayConfig and modetest.
Comment 6 solo24 2020-09-30 17:42:46 UTC 
Created attachment 1717941 [details]
The patch for meta_calculate_drm_mode_refresh_rate.

The attached patch can fix the issue.
Comment 8 RHEL Program Management 2022-03-28 07:30:10 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 9 Jonas Ådahl 2022-03-28 07:56:39 UTC 
Does https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1737 work as well?