|Summary:||system-config-display should show refresh rate.|
|Product:||[Fedora] Fedora||Reporter:||Hans Deragon <hans>|
|Component:||system-config-display||Assignee:||Adam Jackson <ajax>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:|
|Version:||rawhide||CC:||mattdm, mcepl, mcepl|
|Target Milestone:||---||Keywords:||FutureFeature, Triaged|
|Fixed In Version:||Doc Type:||Enhancement|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-05-03 14:51:30 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Hans Deragon 2004-09-10 15:16:54 UTC
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 Description of problem: When selecting a resolution, I always require that I get minimum 75Hz refresh rate. system-config-display does not show what the refresh rate would be for a particular resolution. Therefore I have to select a resolution, quit system-config-display, restart X and see. This is not very user friendly. I suggest that with each resolution selected, the effective refresh rate would show up. This would avoid users going trough this trial and error method to get the best resolution with an acceptable refresh rate. xrandr command line shows the resolutions. The xrandr extensions make it possible for 3rd party tools to fetch the info. Hopefully system-config-display could use this feature to fetch the information, making the implementation easier. Version-Release number of selected component (if applicable): 1.0.14
Comment 1 Paul Nasrat 2004-09-14 09:40:50 UTC
Add to Tracker
Comment 2 Matthew Miller 2005-04-26 15:23:15 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match.
Comment 3 Hans Deragon 2005-04-26 15:34:05 UTC
This issue is still unresolved under FC3.
Comment 4 Matthew Miller 2006-07-10 20:35:52 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Comment 5 Hans Deragon 2006-07-12 00:19:53 UTC
Problem still there in FC5 with updates.
Comment 6 Matěj Cepl 2009-11-05 17:11:05 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Comment 7 Matěj Cepl 2010-02-26 12:23:13 UTC
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Comment 8 Matěj Cepl 2010-05-03 14:51:30 UTC
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.