logo and icons in the installer boot splash are distorted
Bug #536692 reported by
Michael Forrest
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gfxboot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
gfxboot-theme-ubuntu (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Lucid |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gfxboot-
The screen resolution needs to be taken into account when displaying the Ubuntu logo and icons so that no distortion of the images occurs.
Related branches
tags: | added: gloam |
Changed in gfxboot-theme-ubuntu (Ubuntu Lucid): | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → ubuntu-10.04-beta-2 |
Changed in gfxboot-theme-ubuntu (Ubuntu Lucid): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in gfxboot-theme-ubuntu (Ubuntu): | |
assignee: | Colin Watson (cjwatson) → nobody |
Changed in gfxboot-theme-ubuntu (Ubuntu Lucid): | |
assignee: | Colin Watson (cjwatson) → nobody |
To post a comment you must log in.
I don't think we'll be able to get this perfect; trying to do image scaling in gfxboot is, well, unlikely to produce good results, and a bad idea anyway (see below). The best I think we can do is to try to pick the VESA mode that's closest in shape to what gfxboot's monitorsize primitive returns. I'm not sure that that equates to actual native panel resolution on laptops, though; figuring that out involves a whole load of chipset-specific code that gfxboot simply doesn't have.
Without knowing the native panel resolution, there's no way for gfxboot- theme-ubuntu to guess what scaling the hardware is applying to the video mode and reverse it, not that this would be a good idea anyway; some hardware will simply centre a small video mode in the available screen space, whereas some hardware will scale it. We have no way to know what the hardware is going to do here.
Note that this is completely different from things like widescreen themes for xsplash. With things like xsplash themes, we can assume that X has picked a good resolution for the monitor (and X has a *lot* of chipset-specific code to try to do this), so we need different versions of the theme to account for the fact that different resolutions have different shapes if you assume square pixels. That isn't the case here - the problem is one of trying to select a good resolution in the first place, because we don't have all the usual infrastructure.
What we might also be able to do is to get the physical monitor size from a DDC probe (we're already doing the probe; it's just a matter of getting some different information from it - byte 15h is the maximum horizontal size in cm, and byte 16h is vertical) and try to pick a screen size based on that. We'd still be limited to VESA modes, though, and the same caveats about hardware scaling apply.