Description of problem:
prefdm is old, creaky, and causing us problems. No other distribution relies on it anymore, and systemd itself has a clean process for handling display managers, so let's move to that.
For maximum compatibility, we would shift dm.service symlink to point to /etc/systemd/system/display-manager.service, which itself would point to the proper display manager. /usr/lib/systemd/system/display-manager.service should not exist anymore. prefdm.service would not exist anymore. We could ship an override to display-manager.service that always adds the on failure message that we see now with the current prefdm.service if we want.
We would ship in wherever we ship systemd presets something like what Fedora has, which triggers the automatic enablement of a display manager once installed, but won't allow for display managers to be overwritten. Since you only want one to be enabled at a time, this works fine.
The initscripts patches that remove prefdm would be applied instead of not used, and drakdm needs to be tweaked to handle the display-manager.service symlink instead of changing the prefdm configuration.
I have successfully installed via net-install cauldron both i586 and x86_64 (so not an MGA6 upgrade).
unfortunately display manager does not auto-start.
I can "get" to LXDE desktop using "startx startlxde" from a tty2, for example.
This is not a complaint, just a report.
I have also performed Mga6 upgrades to cauldron, and am able to login to desktops via dm greeter without issue (presumably as prefdm.service is still in use)
(In reply to ben mcmonagle from comment #6)
> I have successfully installed via net-install cauldron both i586 and x86_64
> (so not an MGA6 upgrade).
> unfortunately display manager does not auto-start.
See bug 22620
The problem is firstname.lastname@example.org and gui runlevel not enabled during install.
Boot runlevel 3,
login as root.
systemctl enable email@example.com
systemctl set-default graphical.target
Next boot should work.
bug 22593 has the workaround for runlevel 5/gui login.
(In reply to Bit Twister from comment #8)
> bug 22593 has the workaround for runlevel 5/gui login.