Bug 122840 - Handling of non-DDC monitors broken
Summary: Handling of non-DDC monitors broken
Status: CLOSED DUPLICATE of bug 120950
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-display
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-09 02:02 UTC by H. Peter Anvin
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 19:03:08 UTC
Type: ---

Attachments (Terms of Use)

Description H. Peter Anvin 2004-05-09 02:02:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b)

Description of problem:
I have a monitor hooked up via a KVM switch which unfortunately does
not propagate DDC queries.  In FC2test3, this results in a neverending
loop since the system insists on every single boot that my X is not
configured.  It leaves a couple of lines in /etc/X11/xorg.conf:

 ### Uncomment if you don't want to default to DDC:
#       HorizSync    31.5 - 67.0
#        VertRefresh  50.0 - 65.0

Unfortunately, even if I uncomment these manually (which makes X11
work), it still comes back on the next boot and wants me to
reconfigure X11 once again, ad nauseam.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install Fedora with a non-DDC monitor.

Additional info:

I recommend adding a check box to the monitor selection "don't use
DDC"; additionally, whatever it is that tries to detect if the monitor
has changed must respect that and not try over and over to ask for

Comment 1 Andrew Farris 2004-05-14 18:05:38 UTC
Duplicate of #120950 about the DDC commented problem.. but interesting
idea for enhancement for the tool.

Comment 2 Brent Fox 2004-05-17 18:34:33 UTC

*** This bug has been marked as a duplicate of 120950 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:03:08 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.