group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1578442@xxxxxxxxxxxxxxxxxx>]

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.ancell@xxxxxxxxxxxxx>  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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 Released

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