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 <[email protected]> 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 Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1594229
Title:
Not able to use multiple USC instances
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.18 series:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Xenial:
Fix Released
Status in lightdm source package in Yakkety:
Fix Released
Bug description:
[Impact]
If more than one Mir session is running in an xlocal seat LightDM will
attempt to launch one Unity System Compositor per session. This used to work
but now USC only allows a single instance.
[Test Case]
1. Start LightDM
2. Log into a Mir session
3. Switch to the greeter
3. Log into another Mir session (with a second user)
Expected result:
Second session shows.
Observed result:
Can't log in because USC won't start a second time.
[Regression Potential]
Some refactoring was required to make this work, which could cause a
regression. Existing regression tests reduce this risk.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1594229/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp