Description of problem:
even with an extended timeout value (25 sec) firstboot fails to startup when
RHGB is *not* installed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install rawhide excluding RHGB package
I increased the timeout in xfirstboot.py to 25 seconds to ruleout problems with
the Trident Cyberblade/i1 AGP card. Firstboot comes up and displays the Welcome
screen, but clicking the "Forward" button causes firstboot to crash with a
report of "Cannot communicate with window manager" (Don't have the
/tmp/firstboot-crash.txt for this, sorry)
Attempting to run firstboot from a root terminal window also fails with a
"Cannot start any firstboot interface" (or something like that) error.
Additional info: similar problems with old bug, but now it comes up and fails
at the first mouse click.
FC5t3: Firstboot seems to get its X config independently of the xorg.conf file.
This leads to a failure because rhpxl is finding the "wrong" card on my setup
(PCI before AGP - changed behaviour from t1 and t2) and still won't start from
the command line.
rhpxl could probably be changed to allow use of the system X config file.
anaconda also uses rhpxl to get the X configuration, so hopefully the anaconda
file and the firstboot file should be the same. If not, that's a good reason to
make that change to rhpxl.
I think it's probably worth investigating just removing that timeout in
firstboot, too. I've had some success with reproducing this problem, but it's
not regular. Also, sometimes I'm getting the "Cannot communicate" message
spuriously. I think that's probably doing more harm than good.
What's the status of this now with the rhpxl multihead changes that went in on 2/22?
Attempted install today, anaconda bug #182990 prevents testing,
This should be better now.
Tested a rawhide install 2006-03-03 and things went fine without rhgb in the mix.