When installing Mageia 4 on a self made computer with a GeForce 7300 GS (nVidia), after first screens the sync fail and it is impossible to choose any parameters. The screen looks like a zebra skin ;-) For installing Mageia 4, I must install Mageia 3 first and wait for splash screen who say "A new Mageia is available ..." and I reply yes to install Mageia 4 automaticly. Is the same for Mageia 5 ? Have a nice day. Reproducible: Steps to Reproduce:
Always reproductible.
Priority: Normal => release_blockerTarget Milestone: --- => Mageia 4
Why setting it as release blocker for a version already available ? it's useless. > Is the same for Mageia 5 ? Test yourself, beta are for that
*** Bug 15200 has been marked as a duplicate of this bug. ***
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) => NEEDINFOCC: (none) => thierry.vignaudSummary: Bad video sync during instal. => Bad video sync during install
Can't be a release_blocker against Mageia 4. Please try Mageia 5 beta 3 and report if you experience the same issue, then we can start looking at it for our incoming release.
Priority: release_blocker => HighCC: (none) => remi
Hello Yves, any chance you could test Mageia 5RC for this issue?
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
Since we have not received feedback to the information we have requested 4 times 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 => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD