| Summary: | Black and white installation menus in high resolution | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ole Reier Ulland <ole.reier.ulland> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | jarillon, marja11, thierry.vignaud |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Ole Reier Ulland
2015-01-30 07:06:20 CET
The mga4 tree is frozen, there won't be any updates to the installer. Can you try mga5 installer? And provide a screenshot? Keywords:
(none) =>
NEEDINFO Hi Ole Reier Ulland. In comment #1, Thierry Vignaud asked if you could test with Mageia 5 (you can now test with Mageia 5 RC which has been released recently), and provide a screenshot. We can't fix a bug if don't have information about it :) When and if the installation of Mageia can not make use of the mouse I will make an other bug report with all available hardware data. But I have read that this is a known flaw. When and if the installation also not gives the menus I will take pictures of it with a camera, but I do not see how that helps any. It was the installation pages in black and white in higher resolution than they usually are, but all menus just not on the screen. You can take screenshots in the installer by pressing F2. They will be availabld in /root/drakx after installation. I don't know what is your high resolution.
I have a screen iiyama ProLite X83070WQS ModelName "PL3070WQ"
(2560x1600px) an a card nVidia Corporation|Device 0f02.
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce 420 series and later"
Driver "nvidia"
They work with Mageia 5 without any problem .CC:
(none) =>
jarillon 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 (In reply to Marja van Waes from comment #6) > > This bug was filed very long ago, for Mageia 4. Was this bug still valid for > Mageia 5? > Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |