Bug 1732078

Summary: Mutter reports a 120hz panel on Lenovo T480s when only 60hz panel is build in
Product: Red Hat Enterprise Linux 8 Reporter: Oliver Ilian <oliver>
Component: mutterAssignee: Jonas Ådahl <jadahl>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: fmuellner
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-01 07:43:53 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
mutter output
none
xrandr_60hz_selected
none
xrandr_120hz_selected none

Description Oliver Ilian 2019-07-22 16:01:47 UTC 
Description of problem:
Gnome 3.28.2 (RHEL 8) gives a 120hz option in Gnome display settings, but the display is only 60hz.

Mutter reports 120.02hz, while xrandr only reports 60hz for the internal display (see attachments)

Version-Release number of selected component (if applicable):
RHEL 8
Gnome 3.28.2
mutter 3.28.3-19
kernel 4.18.0-80.4.2

How reproducible:
always

Steps to Reproduce:
1. install RHEL 8 on a T480s with FHD panel
2. check hz settings in gnome settings
3.

Actual results:
120hz is selectable

Expected results:
it should only be 60hz and 50hz
Comment 1 Oliver Ilian 2019-07-22 16:02:48 UTC 
Created attachment 1592615 [details]
mutter output
Comment 2 Oliver Ilian 2019-07-22 16:03:07 UTC 
Created attachment 1592616 [details]
xrandr_60hz_selected
Comment 3 Oliver Ilian 2019-07-22 16:03:28 UTC 
Created attachment 1592618 [details]
xrandr_120hz_selected
Comment 6 RHEL Program Management 2021-02-01 07:43:53 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.