steps to complete it: 1. split off from systemd-units => systemd-units-graphical & systemd-units-multiuser 2. have both of those, use the alternative system for default.target 3. have both of those require systemd-units 4. have systemd-units require systemd-units-multiuser and suggest systemd-units-graphical 5. have XFdrake use the alternative system to have X as default or not 6. have installer install systemd-units-graphical only when using CAT_X 7. prefer systemd-units-graphical and it's alternative target by default. still, this seems to be some work, but it'll fix the bug that nongraphical installs still try to start prefdm and an easy way to get back to it. marking it as release_critical since the installer has to be modified.
Priority: Normal => release_blocker
Why are you rising such things now ? We are in release freeze soon and beta has started for a while. So modifying installer now is just non sense and will be postponed for mageia 3
Priority: release_blocker => HighCC: (none) => ennael1Target Milestone: --- => Mageia 3
i brought it up before with colin, but i think he didn't have the time for it. i was planning on spending some time in this and test this locally a bit before committing it. IMHO, the change in the installer is pretty minimal, ie: 1. rpmsrate for CAT_X changes 2. XFdrake adjustment, the checkbox to have X start at boot time, which doesn't work now with systemd anyway... i was thinking of testing this for half a week and put this and commit/submit it next week or something... is this too much?
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
it appeared i still didn't have time for this... putting it on my personal todo list for mga3. i'll need to remember to pick coling's brain, though.
Keywords: NEEDINFO => (none)
I'm not sure this is a big problem anymore to be honest. We default to multi-user.target in the physical packages (just like we defaulted to runlevel 3 in inittab) and the installer will change that to graphical.target if needed (just like it changed inittab to RL5 if needed). So does this really still need that much attention? I certainly do not like the idea of using the alternatives system for default.target. That's just massively overkill here when a simple symlink in /etc will allow the administrator to choose and the installer takes care of this already. The only use case for switching to graphical mode then would be if the user installs a text system and later wants to install the pkgs to "upgrade" it to graphical. In this case I think a simple %post script on some package or other could take care of switching the default target if desired without too much trouble. Probably no need to overcomplicate it. Reducing it's crucial rating for now.
CC: (none) => mageiaSeverity: critical => normal
actually, maybe not, yesterday, i reinstalled my server, and i didn't notice it. so maybe it's still graphical and the graphical fails or whatever... it's still imho too much X stuff is loaded which seems linked to kernel... but that is not this issue... closing as worksforme
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME