Activity log for bug #1575200

Date Who What changed Old value New value Message
2016-04-26 14:06:07 Patrick Monnerat bug added bug
2016-04-26 14:06:07 Patrick Monnerat attachment added Patch for 1.10.6 as described in text https://bugs.launchpad.net/bugs/1575200/+attachment/4647960/+files/lightdm-1.10.6-linklocal.patch
2016-04-26 14:11:46 Robert Ancell lightdm: importance Undecided Medium
2016-04-26 14:11:48 Robert Ancell lightdm: status New Triaged
2016-04-26 15:50:59 Launchpad Janitor branch linked lp:~pm-datasphere/lightdm/lp1575200
2016-04-28 07:04:14 Robert Ancell lightdm: status Triaged Fix Committed
2016-04-28 07:04:17 Robert Ancell lightdm: milestone 1.19.0
2016-04-28 07:04:25 Robert Ancell nominated for series lightdm/1.18
2016-04-28 07:04:25 Robert Ancell bug task added lightdm/1.18
2016-04-28 07:04:47 Robert Ancell lightdm/1.18: milestone 1.18.2
2016-04-28 07:04:49 Robert Ancell lightdm/1.18: importance Undecided Medium
2016-04-28 07:04:52 Robert Ancell lightdm/1.18: status New Fix Committed
2016-04-28 07:04:59 Robert Ancell bug task added lightdm (Ubuntu)
2016-04-28 07:05:08 Robert Ancell nominated for series Ubuntu Xenial
2016-04-28 07:05:08 Robert Ancell bug task added lightdm (Ubuntu Xenial)
2016-04-28 07:05:17 Robert Ancell lightdm (Ubuntu Xenial): status New Fix Committed
2016-04-28 07:05:19 Robert Ancell lightdm (Ubuntu): status New Fix Committed
2016-04-28 07:05:20 Robert Ancell lightdm (Ubuntu): importance Undecided Medium
2016-04-28 07:05:22 Robert Ancell lightdm (Ubuntu Xenial): importance Undecided Medium
2016-04-28 07:07:12 Robert Ancell nominated for series lightdm/1.10
2016-04-28 07:07:12 Robert Ancell bug task added lightdm/1.10
2016-04-28 07:07:12 Robert Ancell nominated for series lightdm/1.16
2016-04-28 07:07:12 Robert Ancell bug task added lightdm/1.16
2016-04-28 07:08:06 Robert Ancell lightdm/1.10: status New Fix Committed
2016-04-28 07:08:08 Robert Ancell lightdm/1.16: status New Fix Committed
2016-04-28 07:08:13 Robert Ancell lightdm/1.16: milestone 1.16.8
2016-04-28 07:08:24 Robert Ancell lightdm/1.10: milestone 1.10.7
2016-04-28 07:09:31 Robert Ancell lightdm/1.16: importance Undecided Medium
2016-04-28 07:09:33 Robert Ancell lightdm/1.10: importance Undecided Medium
2016-04-28 07:09:49 Robert Ancell nominated for series Ubuntu Trusty
2016-04-28 07:09:49 Robert Ancell bug task added lightdm (Ubuntu Trusty)
2016-04-28 07:09:49 Robert Ancell nominated for series Ubuntu Wily
2016-04-28 07:09:49 Robert Ancell bug task added lightdm (Ubuntu Wily)
2016-04-28 07:09:56 Robert Ancell lightdm (Ubuntu Trusty): status New Fix Committed
2016-04-28 07:09:58 Robert Ancell lightdm (Ubuntu Wily): status New Fix Committed
2016-04-28 07:10:03 Robert Ancell lightdm (Ubuntu Trusty): importance Undecided Medium
2016-04-28 07:10:05 Robert Ancell lightdm (Ubuntu Wily): importance Undecided Medium
2016-04-28 08:30:49 Ubuntu Foundations Team Bug Bot tags patch
2016-04-28 08:30:58 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2016-05-02 17:57:10 Rex Dieter bug added subscriber Rex Dieter
2016-05-05 00:40:49 Robert Ancell lightdm: status Fix Committed Fix Released
2016-05-05 02:23:56 Launchpad Janitor lightdm (Ubuntu): status Fix Committed Fix Released
2016-06-21 04:26:48 Robert Ancell lightdm/1.18: status Fix Committed Fix Released
2016-06-21 04:40:39 Robert Ancell description I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses without interface index to connect to X server. It has been originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=1322775. The problem can be fixed by having the XDMCP client not transmitting link-local addresses in the request, but if it does, lightdm XDMCP server can be a lot smarter if the attached patch is applied. It changes the X server address selection order to set the lowest preference to link-local addresses, even if matching the source address or family. This is not 100% full-proof: if only link-local addresses have been received, one of them is used anyway. In this case, a complete solution would be to determine and set the address interface index if not ambiguous. However, this patch fixes the problem for most of the non-pathological cases. [Impact] LightDM doesn't pick the best IPv6 address on offer from clients (picks link-local addresses over non link-local). [Test Case] 1. Start LightDM with XDMCP server enabled 2. Connect XDMCP client that sends IPv6 link-local addresses to LightDM Expected result: LightDM picks a non link-local address and is able to connect to the client Observed result: LightDM picks the link-local address address if it is first [Regression Potential] Small risk of behaviour change due to new IP selection method. Original report: I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses without interface index to connect to X server. It has been originally reported at https://bugzilla.redhat.com/show_bug.cgi?id=1322775. The problem can be fixed by having the XDMCP client not transmitting link-local addresses in the request, but if it does, lightdm XDMCP server can be a lot smarter if the attached patch is applied. It changes the X server address selection order to set the lowest preference to link-local addresses, even if matching the source address or family. This is not 100% full-proof: if only link-local addresses have been received, one of them is used anyway. In this case, a complete solution would be to determine and set the address interface index if not ambiguous. However, this patch fixes the problem for most of the non-pathological cases.
2016-06-23 21:03:10 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2016-06-23 21:03:12 Brian Murray bug added subscriber SRU Verification
2016-06-23 21:03:24 Brian Murray tags patch patch verification-needed
2016-07-13 06:19:16 Launchpad Janitor lightdm (Ubuntu Xenial): status Fix Committed Fix Released