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://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 Committed
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/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to