Red Hat Bugzilla – Bug 74745
X starting up in a different resolution than expected makes font dpi incorrect
Last modified: 2007-04-18 12:46:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; SunOS 5.8 sun4u)
Description of problem:
Installing Redhat 8.0 on a Dell Inspiron 5000E laptop in graphic mode,
anaconda will not let the user past the select the software mode screen. Make a
selection, hit next and NOTHING happens, (it should go to the partition
section). This can be repeated over and over. Work around, use the TEXT
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to install in graphic mode
Actual Results: Once the software selection has been made, next is hit, the
'gray' out and NOTHING happens.
Expected Results: See the parition selection screen.
Does anaconda do anything with the parition table before starting the select
parition mode screen?
Everything works FINE in text mode!
What is the name of the screen you are having difficulty getting past? I am not
sure which software selection screen you are referring to.
The screen that allows you to select the Personal Desktop, Workstation, and etc.
In graphic install this is the screen just before the parition manager choices
Does it work if you hit 'Alt-N' instead?
Oddly enough the ALT-N does work. What is going on?
Is there anything you want me to capture to help you?
Another thing I noticed is that on some screens the mouse click does work on the
NEXT button, but others it does not and I am forced to use ALT-N. I just
completed a graphic install as I type this.
What's going on is that X started at a different resolution than the one we
asked for. Therefore, the font sizes are off from what they should be coupled
with a few event boxes which are done in a slightly non-standard fashion leads
to the button bar not getting focus.
Work around for now is to use alt-N or other keyboard nav if it happens...
we'll look into trying to get a better fix
Yep, you are right on the FONT/RESOLUTION stuff, things are wacked a bit, but
I don't remember these problems with the VESA based install from 7.3.
*** This bug has been marked as a duplicate of 72760 ***
Time tracking values updated