Bug 13012 - During M4.1 Classic Installer not understanding all terminal resolutions
Summary: During M4.1 Classic Installer not understanding all terminal resolutions
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: (MGA4.1)
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-03-13 17:41 CET by William Kenney
Modified: 2016-06-05 15:28 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description William Kenney 2014-03-13 17:41:39 CET 
In the latest M4.1 Classic Installers ie:

Mageia-4.1-i586-DVD.iso    MD5: 0beda1741527547dd959a7a287205fc8
Mageia-4.1-x86_64-DVD.iso  MD5: 70ed516c4a0188c31aebddde5205c701

The latest Classic Installers, named above, when installed in Vbox they do
not completely decode the available number of screen resolutions available.
My monitors highest available resolution is 1920x1200 but the highest
made available after a complete install is 1600x1200. This is during
the install if you allow the installer to use "Plug-n-Play" for resolution.
If you select Custom, LCD, generic and 1920x1200 then indeed this resolution
is made available and can be used.

In the case of the Live media ( DVD & CD ) the installer does in fact
select 1920x1200 automatically.

Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-05-02 19:36:31 CEST 
Hi Will, as you know we can't fix the Mageia 4.1 installer, but is this bug still valid in Mageia 5 RC?

Keywords: (none) => NEEDINFO

Comment 2 Marja Van Waes 2015-09-21 10:51:34 CEST 
Installer and Release bugs should always be set to cauldron, because once the isos for a stable version have been created, they cannot be changed.

This bug was filed very long ago, for Mageia 4. Was this bug still valid for Mageia 5?

(If so, please do _not_ set the version to "5". Only asking because if it was still valid for Mageia 5, that then we'll know we'll have to pay attention to this issue when testing the 6 alpha's and later).

Please close this bug report if the problem was solved in Mageia 5hhhh

Version: 4 => Cauldron

Comment 3 Rémi Verschelde 2015-09-21 11:27:41 CEST 
Does it also happen on real hardware, or is it Vbox specific?
Comment 4 Marja Van Waes 2016-02-17 20:30:27 CET 
@ Wilcal

Is this bug valid for 6dev1?

CC: (none) => marja11
Whiteboard: (none) => (MGA4.1)

Comment 5 William Kenney 2016-02-17 22:53:43 CET 
(In reply to Marja van Waes from comment #4)
> @ Wilcal
> 
> Is this bug valid for 6dev1?

I can't say as I've not been able to get any version of 6dev1 up
and running on hardware of Vbox. So I'll put this in my things to
look at when we get something M6 that works.
Comment 6 Marja Van Waes 2016-06-05 14:11:56 CEST 
(In reply to William Kenney from comment #5)
> (In reply to Marja van Waes from comment #4)
> > @ Wilcal
> > 
> > Is this bug valid for 6dev1?
> 
> I can't say as I've not been able to get any version of 6dev1 up
> and running on hardware of Vbox. So I'll put this in my things to
> look at when we get something M6 that works.

And?
Comment 7 William Kenney 2016-06-05 15:28:44 CEST 
This is long since fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.