Michael Biebl [2014-12-02 14:33 +0100]: > Those are bugs in the lxdm and slim packages and need to be fixed there.
That'd be my preference too, TBH, but it was already n'acked by the RT. Maybe we can reopen this, though. > Trying to workaround that in systemd looks like the wrong approach. The whole "configure your default DM" has become horribly complicated in Debian :-( sysvinit and systemd both have their own ways of enabling/disabling services, and on top of that we still have this /etc/X11/default-display-manager thing which potentially collides/disagrees with those, so I don't think there ever is a way to get this right. But with the current situation of having to support multiple inits and multiple DMs, I think that /etc/X11/default-display-manager should be the configuration which trumps systemctl enable/update-rc.d disable/enable, and thus we need some central place to tell how to translate that file to a particular boot sequence. So while the DM packages certainly should be fixed to get a proper unit, that still wouldn't completely fix the problems here -- we still need something to sync /e/X/d-d-m with the init system specific enabling/disabling. So the idea of that generator isn't too bad or only a workaround IMHO. However, it's been shown to be quite complex, so before we land this in jessie I'd like to give it some more maturing in experimental. If it turns out to cause more damage than good, we can rip it out again and say "*sigh* don't do that then", if people try to be too clever with configuring their DMs.. But Michael, I don't want to go over your head here. If you don't like this at all, then let's stop this right away instead of risking more debugging/work on this? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
