Description of problem: After a fresh install of M2b3, a minimal install without X so console only, after boot a graphical login is attempted. As the X hasn't been installed that fails with the display of message from display-manager-failure-message script. The error is benign as it drops to console, which it should do in first place. System shouldn't assume a graphical login. Version-Release number of selected component (if applicable): Dual iso of M2b3 How reproducible: Install system as console only
I guess it's a duplicate of bug 2038, you can add manually "text" in the kernel command line *** This bug has been marked as a duplicate of bug 2038 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
I've looked at the 2038, but that one it's specifically related to installer. The issue reported relates to system _after_ install. Then when booting, with framebuffer or not, system assumes graphical login. Addition of text kernel boot option to grub config didn't change the behavior. So i doesn't look to be duplicate of 2038.
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)
ah sorry read to fast :/
CC: (none) => mageia, thierry.vignaudComponent: Installer => RPM PackagesSource RPM: (none) => systemd
Yeah this happens because systemd-units is installed by the installer before initscripts. I've made systemd install default to multi-user.target for now and the installer should already take care to change that to the correct target if you configure the graphics during install.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Also you could add conflicts: initscripts < some_older_version to systemd-units to force package ordering
(In reply to comment #5) > Also you could add conflicts: initscripts < some_older_version to systemd-units > to force package ordering Would that help in the installer for a fresh install. The problem was that systemd-units is installed *before* initscripts and thus /etc/inittab does not exist for us to base the default.target symlink on and we defaulted to graphical.target. Adding a conflicts would (in my perhaps limited understanding) not help to get initscripts installed earlier? It would surely need a "Requires(post): initscripts" to achieve this? I did think to do this but as /etc/inittab will die off in mga3, I felt this was the cleaner solution.