Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 110805 - installclass.py has no "xconfig" default
Summary: installclass.py has no "xconfig" default
Keywords:
Status: CLOSED DUPLICATE of bug 105586
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-24 16:29 UTC by Joshua Jensen
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Joshua Jensen 2003-11-24 16:29:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030807


Description of problem:
The docs say that xconfig doesn't have to have the --card or --monitor
arguments, and if left out anaconda would use what is found when
probing. I can see that my monitor and video card are ddcprobed for, and
detected perfectly.... but anaconda complains that it didn't find any
sane defaults, and says this when "xconfig" is on a line by itself:

File "user/lib/anaconda/installclass.py", line 461, in configureX
  self.setMiscXSettigns(id, depth, resolution, runlevel = rl)
File "/usr/lib/anaconda/installclass.py", line 366, in setMiscXsettings
  id.xsetup.xhwsetup.choose_sane_default()
AttributeError:  XSetup instance has no attribute 'xhwsetup'



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


How reproducible:
Always

Steps to Reproduce:
1. Make a valid ks.cfg file, test it to be sure it works
2. remove all args to the xconfig line in said ks.cfg
3. watch anaconda traceback =)
    

Expected Results:  According to the docs, xconfig needs no arguments.
 Can Red Hat please fix this... I could see this being a sensible
logic path:

1)  Use the monitor/card specified to xconfig in ks.cfg, else

2)  autodetect monitor/card and uses that to match the list of known
monitors/cards, then use the specs from the matching entries on the
list, else

3)  use the raw dccprobe specs for monitor, detect or guess card, else

4)  with no information whatsoever, (but "^xconfig$" still present in
ks.cfg), choose super-generic defaults for monitor/card.

Additional info:

I can actually use the installer from Fedora if this is fixed there...
please provide feedback regardless.

Comment 1 Jeremy Katz 2003-11-24 22:17:55 UTC
This is in the queue of things for the first update (and is fixed in
FC1 since that's a later codebase)

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:00:09 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.