> I'm not sure how this would have worked in the past. Ah, I know now -- when I do "sudo apt-get install --no-install- recommends lightdm" in xenial, lightdm.service is not started at all right after package installation.
So I think that's the regression -- I don't think it's a good idea to start a DM right after package installation, it might interfere with other DMs or running X sessions? Was that done on purpose? > What's pulling in LightDM? Perhaps we should change that depends. Some systemd autopkgtests pull in lightdm, mostly to ensure that boot works and lightdm comes up. In the "real" tests X.org gets configured with the dummy driver and the VM gets rebooted, so lightdm starts up fine. In the test that failed (cmdline-upstart-boot) I don't do this. But I don't install recommends there, thus I run into the "missing greeter" issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581106 Title: [yakkety regression] lightdm fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581106/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
