This bug was fixed in the package lightdm - 1.18.2-0ubuntu1
---------------
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium
* New upstream release:
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
socket to sessions. This used to work but no longer works in Mir 0.21
(LP: #1583624)
- Use only a single compositor on xlocal seats (LP: #1594229)
- Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
- Set XDMCP hostname field in to system hostname or configured value
(LP: #1578442)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix uninitialized memory errors
* debian/lightdm.dirs:
- Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
/etc/guest-session exist
* debian/guest-account.sh:
* debian/guest-session-setup.sh:
- Source prefs.sh as privileged user to allow user modification
(LP: #1581853)
-- Robert Ancell <robert.anc...@canonical.com> Tue, 21 Jun 2016
12:49:01 +1200
** Changed in: lightdm (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
