Bug 770874

Summary: no utility to set monitor type or display resolution
Product: [Fedora] Fedora Reporter: Max Kessler <cyberman>
Component: xfce4-settingsAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: kevin, maxamillion, rosset.filipe, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 01:33:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Xorg.0.log file with KVM switch attached
none
Xorg.0.log file with monitor directly connected to computer none

Description Max Kessler 2011-12-29 22:01:09 UTC
Description of problem:
The absence of system-config-display removes the user friendly way to configure a monitor type and display resolution.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.11.1-1.fc16.i686

How reproducible:
always

Steps to Reproduce:
1. Install anything newer than Fedora 13 with a graphical desktop.
2. Note the absence of any utility to specify a monitor type and resolution.
3. Note that the closest is a setting in XFCE that only includes 1024x768, 800x600, and 640x480 even though my monitor is 1600x900 and the video cards in my Fedora 16 boxes should support widescreen.  One of them was using widescreen in Ubuntu, but I got rid of that, because it didn't support root fs encryption.
4. Pound your head on the wall as you are unable to find relevant search results.
5. Give short lived consideration to going back to Windows, but remember that Microsoft is somewhat worse than Red Hat about system requirements.
  
Actual results:
XFCE display settings manager only presents a small handful of aspect resolutions, none larger than 1024x768.  There is no way to specify a monitor type.

Expected results:
system-config-display (or some similar tool) should present users with a list of known monitor types, including generics like "Generic LCD 1600x900".

Additional info:
I tried rebuilding system-config-display from the most recent SRPM, but it wants HAL, which doesn't appear to exist any more either.

My monitor has an optimal resolution of 1600x900.  The video card on my primary system is: VGA compatible controller: ATI Technologies Inc Radeon 3100 Graphics
The video card on my secondary system is: VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01)

The secondary system was running Ubuntu 9.10 with a wide aspect, but less than 1600x900.

Comment 1 Adam Jackson 2012-02-09 18:00:36 UTC
s-c-d is not coming back.  This is the DE's job.

Comment 2 Kevin Fenzi 2012-02-09 21:13:08 UTC
Please attach your /var/log/Xorg.0.log ? Xfce's display applet here is showing the display sizes from xrandxr, and I suspect that you have 'nomodeset' or the like so you get a reduced resolution size available.

Comment 3 Max Kessler 2012-02-11 14:48:40 UTC
Created attachment 561097 [details]
Xorg.0.log file with KVM switch attached

This is the Xorg.0.conf file with the KVM switch attached.

Comment 4 Max Kessler 2012-02-11 14:54:24 UTC
Created attachment 561098 [details]
Xorg.0.log file with monitor directly connected to computer

This is the Xorg.0.conf file after I manually unplug the monitor from the KVM switch and the KVM switch from the computer and plug the monitor directly into the computer.

Comment 5 Max Kessler 2012-02-11 15:10:12 UTC
When I plug the monitor directly into one of the computers and boot, I can reconnect the KVM switch after Xorg starts and it continues to work fine.  What I need is some way to tell Xorg to ignore any information received from the KVM switch and use the settings specified in /etc/X11/xorg.conf (including disabling DPMS and DontZap).  I generated the xorg.conf file by running "Xorg -configure" without the KVM switch attached and manually added options to disable DPMS and DontZap.

Again, Ubuntu 9.?? supported wide screen without any hassle.

Comment 6 Kevin Fenzi 2012-02-12 00:15:59 UTC
Whats in your /etc/X11/xorg.conf file? 

If you remove (or move it aside) does the behavior change?

Comment 7 Fedora End Of Life 2013-01-16 23:07:53 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-14 01:33:28 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.