Bug 64695 - Xconfigurator --kickstart fails to create config file
Xconfigurator --kickstart fails to create config file
Status: CLOSED DUPLICATE of bug 39745
Product: Red Hat Linux
Classification: Retired
Component: Xconfigurator (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-05-09 15:24 EDT by Peter Fales
Modified: 2006-03-10 22:12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:48:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Here's a specific patch for 4.10.7-1 that makes it work for us. (1.69 KB, patch)
2002-08-12 18:33 EDT, andrew m. boardman
no flags Details | Diff

  None (edit)
Description Peter Fales 2002-05-09 15:24:54 EDT
Description of Problem:

When I run "Xconfigurator --kickstart" to automate the creation of the 
XF86Config-4 file, it fails.   Investigation reveals that it is failing to 
probe the amount of memory available, and that looks to be due to a change
in the way XFree86 4.2 handles debug output.  

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


How Reproducible:

Consistently reproducable

Steps to Reproduce:
1. Remove /etc/X11/XF86Config-4
2. run "Xconfigurator --kickstart"

Actual Results:

No /etc/X11/XF86Config-4 file is created

Expected Results:

An /etc/X11/XF86Config-4 file should be created

Additional Information:
In examining the Xconfigurator source code, it looks like it is running
"Xfree86 --probeonly" and grepping stderr for the string "videoRAM: ".  This
worked under XFree86 4.0, but under 4.2, the debug output goes to a logfile
instead of stderr.  I was able to get Xconfigurator to work by replacing
all the lines that look like

	Xconfigurator --probeonly ... 2> tmpfile


	Xconfigurator --probeonly ... -logfile tmpfile 2> /dev/null
Comment 1 Mike A. Harris 2002-05-30 18:17:01 EDT
*** Bug 65487 has been marked as a duplicate of this bug. ***
Comment 2 andrew m. boardman 2002-08-12 18:33:07 EDT
Created attachment 70164 [details]
Here's a specific patch for 4.10.7-1 that makes it work for us.
Comment 3 Isaiah Weiner 2002-12-21 14:05:24 EST
When can an errata be expected?  This is an issue with Cisco, as well.
Comment 5 Mike A. Harris 2003-04-20 13:04:46 EDT

*** This bug has been marked as a duplicate of 39745 ***
Comment 6 Red Hat Bugzilla 2006-02-21 13:48:52 EST
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.