Public bug reported:

[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.

** Affects: lightdm
     Importance: Medium
         Status: Fix Committed

** Affects: lightdm/1.10
     Importance: Medium
         Status: Fix Committed

** Affects: lightdm/1.16
     Importance: Medium
         Status: Fix Committed

** Affects: lightdm/1.18
     Importance: Medium
         Status: Fix Committed

** Affects: lightdm/1.2
     Importance: Medium
         Status: New

** Affects: lightdm (Ubuntu)
     Importance: Medium
         Status: Triaged

** Affects: lightdm (Ubuntu Trusty)
     Importance: Medium
         Status: Triaged

** Affects: lightdm (Ubuntu Wily)
     Importance: Medium
         Status: Triaged

** Affects: lightdm (Ubuntu Xenial)
     Importance: Medium
         Status: Triaged

** Also affects: lightdm/1.18
   Importance: Undecided
       Status: New

** Also affects: lightdm/1.2
   Importance: Undecided
       Status: New

** Also affects: lightdm/1.10
   Importance: Undecided
       Status: New

** Also affects: lightdm/1.16
   Importance: Undecided
       Status: New

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: lightdm (Ubuntu Wily)
   Importance: Undecided
       Status: New

** Also affects: lightdm (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: lightdm (Ubuntu Wily)
       Status: New => Triaged

** Changed in: lightdm (Ubuntu Trusty)
       Status: New => Triaged

** Changed in: lightdm (Ubuntu)
       Status: New => Triaged

-- 
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 Committed
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 Committed
Status in Light Display Manager 1.2 series:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

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