Bug 20575

Summary:	Mageia Cauldron Installer (Sta2) does not detect the right screen resolution.
Product:	Mageia	Reporter:	Sébastien B. <sb.cw>
Component:	Installer	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-kbd-mouse-x11	CVE:
Status comment:

Description Sébastien B. 2017-03-26 18:58:08 CEST

Description of problem:
Mageia Cauldron Installer (Sta2) does not detect the right screen resolution, 1920*1080 on Samsung S24D390, during the installation phase.
The windows are offset, and it is difficult to validate a choice.


Version-Release number of selected component (if applicable):Mageia-6-sta2-x86_64-DVD.iso


How reproducible:


Steps to Reproduce:
1.
2.
3.

Nicolas Lécureuil 2017-03-26 23:06:08 CEST

CC: (none) => mageia
Assignee: bugsquad => mageiatools

Comment 1 Thierry Vignaud 2017-03-27 09:16:03 CEST

What do you mean?
- the resolution while installing
- or the resolution once the just installed system has booted?

Care to attach a screenshot?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud
Source RPM: (none) => drakx-kbd-mouse-x11

Comment 2 Sébastien B. 2017-03-27 09:27:22 CEST

Hello Thierry,

The resolution while installing...

Is not easy to make a screenshoot, in installing mode....

Same problem like:

http://blog.mageia.org/fr/

"Les tests de correctifs sont en cours, nous avons réalisé une nouvelle diffusion dâISO en interne pour tests et vérification de la situation de certains bogues de lâinstalleur, tels que lâapparition de boutons en dehors de lâécran Ã  lâétape du partitionnement dans certaines langues"

But not only for the partitionnement...

Regards,

Sébastien B.

Comment 3 Thierry Vignaud 2017-03-27 14:32:30 CEST

The installer uses the generic fbdev or vesa drivers and with a resolution of either 1024x768 in the usual case.
As for the off window bug, this has already been fixed on March 17th in drakx-installer-stage2-17.75

*** This bug has been marked as a duplicate of bug 20360 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE