Testing in VirtualBox with an earlier Mageia Installation on the vdi, a new net-install using the "Erase and use entire disk" option fails to do so. I twice tried to install a full KDE over a minimal LXDE installation and it appeared to do an update install in around 30 seconds. The repeat was just to be sure of the options I had chosen - same result. I will repeat the test in a different vdi to confirm.
Confirmed on disk (vdi) with a clean LXDE installation on it. Selected KDE again with all default options to erase and use entire disk. Install (NOT update) Use entire disk Confirmed that all data on sda will be lost Formatting screens flash past and then the install takes around 40 seconds- not even time for a brew! User info then: "The package XDM needs to be installed do you want to install it?" The only options are previous and next. - Next Another 1 min of what look like base libs, X11 stuff, oxygen.... Summary shows Graphical interface not configured. Clicking Configure against Graphical interface instantly starts to install another batch of around 54 packages - and then drakx11 runs after which it's back at the summary from where the install then completes OK. Graphical login fails, but booting into run level 3 does allow me to confirm that no KDE packages are installed. As root systemctl start prefdm.service goes back to the very basic (ICEWM?) graphical login I had before but it again fails and keeps returning. (not numlock I checked ;) What a mess!
I failed to mention that these were net-installs using boot.iso
have you enough disk place on your vdi ? ie what to you have before the first unselecting ... in /root/drakx/ddebug.log ? personnaly I have a "too big for level 5... " so in fact it does but a minimal install instead of a full kde one there could be workaround with bug 3189 for the xdm part: bug 4809
Both vdi were 8GB dynamic and in the one system I can access there is only 23% of / in use. / 4GB (used 874MB) /home 3.3GB (used 6MB) I will try to get at the logs later when I have more time, but the default drive size allocation looks reasonable.
4Go is not enough, it's really a duplicate of bug 3189
Created attachment 3587 [details] ddebug.log from installed system Yes it looks that way - here is the ddbug.log
ok *** This bug has been marked as a duplicate of bug 3189 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE