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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #11 from Olivier Fourdan <fourdan at xfce.org> ---
(In reply to Pekka Paalanen from comment #10)
> 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.

Possibly, but that wouldn't be an Xwayland bug, more of a wider, general
Xserver bug in xserver/os/ code - Basically, I would expect the same to occur
with Xorg (I haven't tried though), unless there is something special about
Xwayland.

I think the bug here would be that the messages are repeated.

> 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

Yes to both questions, this is the "-displayfd" option that kwin uses:

> 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?

Xorg/Xwayland will acquire the lock as it always do in the "normal" case, I do
not see this as a bug in kwin.

-- 
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/20180601/cdf666a3/attachment.html>