[Wayland-bugs] [Bug 106573] When kwin_wayland tries to start XWayland, XWayland hangs with endless inet6-related errors

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 31 09:13:25 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106573

--- Comment #10 from Pekka Paalanen <ppaalanen at gmail.com> ---
Right, so regardless of whether it's good or bad to enable listening on TCP/IP,
however that was done, there is still the original problem, right?

So this bug report becomes: When TCP/IP is enabled, there is endless log spam
about failures if kernel IPv6 is disabled. That seems like a legitimate bug to
me, unless Xorg has decided to require IPv6.

The other thing: if not using -listen command line option, should Xwayland find
a free display number itself? Does it have a way to communicate it back to the
parent process? Or is the parent process required to find a free display
number, which means the parent process is always required to handle the lock
file itself, and there should be a kwin bug report about it?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20180531/b490c2d7/attachment.html>


More information about the wayland-bugs mailing list