group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #03069
[Bug 1575200] Re: Error connecting to X server via IPv6
This bug was fixed in the package lightdm - 1.19.0-0ubuntu1
---------------
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium
* New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
(LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
* debian/rules:
- Fix usage of dh_installinit (LP: #1292990)
-- Robert Ancell <robert.ancell@xxxxxxxxxxxxx> Thu, 05 May 2016
12:23:45 +1200
** Changed in: lightdm (Ubuntu)
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/1575200
Title:
Error connecting to X server via IPv6
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 Committed
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Trusty:
Fix Committed
Status in lightdm source package in Wily:
Fix Committed
Status in lightdm source package in Xenial:
Fix Committed
Bug 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1575200/+subscriptions