← Back to team overview

touch-packages team mailing list archive

[Bug 1511545] Re: Implement XDMCP ForwardQuery

 

This bug was fixed in the package lightdm - 1.16.5-0ubuntu1

---------------
lightdm (1.16.5-0ubuntu1) wily; urgency=medium

  * New upstream release:
    - Handle trailing whitespace on boolean values in configuration.
      (LP: #1507033)
    - Add a backup-logs option that can be used to disable existing logging
      files having a .old suffix added to them.
    - Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and
      LC_IDENTIFICATION variables to the list of inherited locale variables.
      (LP: #1511259)
    - Implement XDMCP ForwardQuery. (LP: #1511545)
    - Fix small memory leak in XDMCP logging code.
    - Check the version of the X server we are running so we correctly pass
      -listen tcp when required. (LP: #1449282)

 -- Robert Ancell <robert.ancell@xxxxxxxxxxxxx>  Tue, 03 Nov 2015
16:47:08 +1300

** Changed in: lightdm (Ubuntu Wily)
       Status: Fix Committed => Fix Released

-- 
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/1511545

Title:
  Implement XDMCP ForwardQuery

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  LightDM ignores the XDMCP ForwardQuery request.

  [Test Case]
  1. Set up XDMCP so queries are forwarded through a server
  2. Connect to LightDM

  Observed result:
  Connection fails

  Expected result:
  Connection succeeds.

  [Regression Potential]
  Some risk of existing XDMCP queries being broken by the change. Checked with regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1511545/+subscriptions