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!

** Changed in: lightdm (Ubuntu Xenial)
       Status: Triaged => Fix Committed

** 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/1578442

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1578442/+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