Bug 394431 - KWin hangs forever when trying to start with XWayland with inet6-related errors
Summary: KWin hangs forever when trying to start with XWayland with inet6-related errors
Status: CLOSED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: platform-x11-nested (show other bugs)
Version: 5.12.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-19 04:46 UTC by Kyle Devir
Modified: 2018-05-19 05:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle Devir 2018-05-19 04:46:54 UTC 
This happens when I start KWin from the VT using startplasmawayland, or starting a nested kwin_wayland using the --xwayland option.

I get this error repeated endlessly:

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/valmar-desktop:15579
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

Additionally, I run a custom Arch kernel with IPv6 disabled, because it has caused mysterious DNS resolution slowdown for me in the past.
Comment 1 Kyle Devir 2018-05-19 04:49:16 UTC 
According to another forum's post on a similar issue, -nolisten inet6 solves this issue. Would be nice to be able to customize some of the options passed to Xwayland by KWin, if possible.
Comment 2 Kyle Devir 2018-05-19 04:51:34 UTC 
Also, I am running Xwayland 1.20.0 and Qt5 5.11.0rc2 on Arch Linux.
Comment 3 Martin Flöser 2018-05-19 05:09:05 UTC 
Please report to xwayland that it doesn't show these warnings. We are not going to add functionality to customize xwayland command arguments.
Comment 4 Kyle Devir 2018-05-19 05:26:21 UTC 
I've reported this upstream.

You're correct that it is unreasonable to expect KWin to workaround this. :/