Red Hat Bugzilla – Bug 73468
Anaconda gets the wrong DPI if you can't run X in 800x600
Last modified: 2013-04-02 00:17:04 EDT
If X doesn't like either of the modes that anaconda provides in its XF86Config
file, then it will pick its own resolution. As a result, the font size is too
big when anaconda starts. When you finally reach the Install/Update screen, it
results in the radio buttons appearing behind the 'Back/Next' buttons, and
preventing you from clicking on them. It has the added side-effect of making
the screen insensitive, making it look like you've gone forward and hung.
It would be good to pick a different DPI if the resolution given isn't the one
To clarify -- we get confused when we explicitly put 800x600 as the resolution
in the config file, but X then decides "oh, I don't want you to do that" and
starts up in 1024x768 instead :/
Which means that our carefully calculated DisplaySize ends up being wrong (and
dpi is 123x123 or something along those lines)
See if we'd tried to hit 85 dpi like I said it would have still worked ok :)
Created attachment 75045 [details]
Log file of starting X
Created attachment 75046 [details]
XF86Config file provided by anaconda
Attached logs from my install for posterities sake.
To change the DPI once we've imported gtk, we can just call:
Note that 12345 is 1024*desired_dpi
*** Bug 76122 has been marked as a duplicate of this bug. ***
I should have this fixed now.
Time tracking values updated
I'm going through Bugzilla closing some bugs that have been marked as Modified
for some period of time. I believe that most of these issues have been fixed,
so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists,
please reopen this report and mark it as Reopened.