<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - When kwin_wayland tries to start XWayland, XWayland hangs with endless inet6-related errors" href="https://bugs.freedesktop.org/show_bug.cgi?id=106573#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - When kwin_wayland tries to start XWayland, XWayland hangs with endless inet6-related errors" href="https://bugs.freedesktop.org/show_bug.cgi?id=106573">bug 106573</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>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?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>