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
soc
Fixed in Xenial.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594229
Title:
Not able to use multiple USC instances
To manage
Hello Robert, or anyone else affected,
Accepted lightdm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Changed in: lightdm/1.18
Status: Fix Committed => Fix Released
** Changed in: lightdm (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Description changed:
- LightDM currently uses one Unity System Compositor instance per Mir
- session for the xlocal seat. This is not allowed
** Changed in: lightdm/1.18
Milestone: None => 1.18.2
** Changed in: lightdm/1.18
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594229
Title:
Not able t
This bug was fixed in the package lightdm - 1.19.1-0ubuntu1
---
lightdm (1.19.1-0ubuntu1) yakkety; urgency=medium
* New upstream release:
* debian/lightdm.dirs:
- Rename "xlocal" seat type to "local". Using "xlocal" will continue to work
but report a warning.
- Ensur
** Changed in: lightdm
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/1594229
Title:
Not able to use multiple USC instances
To manage notifications about
