Bug 377751 - Resolution not detected in initial GTK installation part
Resolution not detected in initial GTK installation part
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-12 08:43 EST by Dave Crossland
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-12 11:31:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Crossland 2007-11-12 08:43:22 EST
Description of problem: Anaconda's GTK installation appears to run at a low
resolution like 640x480 or 800x600, and on my 24" widescreen LCD monitor, the
subpixel hinting on the text looks really weird and the pixel images are very
blocky. FirstBoot correctly detects the monitor size and so on though (although
I guess this is because X is running then)

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

How reproducible: Always

Steps to Reproduce:
1. Install Fedora 8 on a computer with a high resolution screen that scales up
lower resolutions.
Actual results: Anaconda has a fixed low resolution

Expected results: Anaconda detects the resolution of the monitor like X windows
and uses it, so that text and images are displayed properly.
Comment 1 Chris Lumens 2007-11-12 11:31:37 EST
The overall UI in anaconda isn't really designed to be run at a resolution
higher than 800x600.  If you choose to run it at some larger resolution, it will
look funny because widgets will be huge, there will be even more blank space,
and so forth.  If you do need to run anaconda at a higher resolution, it's a
simple matter of adding the resolution= parameter to your boot args.

Note You need to log in before you can comment on or make changes to this bug.