_XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777

[rye2020]

Windows Version

Microsoft Windows [Version 10.0.27686.1000]

WSL Version

WSL version: 2.3.17.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.64 MSRDC version: 1.2.5326 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.27686.1000

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.133.1-microsoft-standard-WSL2 (jrm@OPX3050) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP Sun Oct 15 09:17:36 EDT 2023

Distro Version

Release: 24.04

Other Software

none

Repro Steps

Simply start Ubuntu. Syslog begins with error messages.

Expected Behavior

No error message.

Actual Behavior

Loop on error message: XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failedls

Diagnostic Logs

2024-08-20T07:45:24.841669-04:00 OPX3050 systemd[1]: Started pmlogger_farm_check.service - Check and migrate non-primary pmlogger farm instances.
2024-08-20T07:45:24.853994-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777
2024-08-20T07:45:24.874106-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketCreateListener: failed to bind listener
2024-08-20T07:45:24.874164-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
2024-08-20T07:45:24.874189-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix
2024-08-20T07:45:24.881272-04:00 OPX3050 wireplumber[3262]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
2024-08-20T07:45:24.886343-04:00 OPX3050 wsl-pro-service[1237]: #33[36mINFO#033[0m Daemon: connecting to Windows Agent
2024-08-20T07:45:24.888960-04:00 OPX3050 wsl-pro-service[1237]: #33[37mDEBUG#033[0m Updated systemd status to "Connecting"
2024-08-20T07:45:24.889009-04:00 OPX3050 wsl-pro-service[1237]: #33[33mWARNING#033[0m Daemon: could not connect to Windows Agent: could not get address: could not read agent port file "/mnt/c/Users/jrmar/.ubuntupro/.address": open /mnt/c/Users/jrmar/.ubuntupro/.address: no such file or directory
2024-08-20T07:45:24.889027-04:00 OPX3050 wsl-pro-service[1237]: #33[36mINFO#033[0m Reconnecting to Windows host in 60 seconds
2024-08-20T07:45:24.889052-04:00 OPX3050 wsl-pro-service[1237]: #33[37mDEBUG#033[0m Updated systemd status to "Not connected: waiting to retry"
2024-08-20T07:45:24.963728-04:00 OPX3050 wireplumber[3262]: BlueZ system service is not available
2024-08-20T07:45:24.971852-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777
2024-08-20T07:45:24.990667-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketCreateListener: failed to bind listener
2024-08-20T07:45:24.990743-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
2024-08-20T07:45:24.990763-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix
2024-08-20T07:45:24.997432-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777
2024-08-20T07:45:25.007310-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketCreateListener: failed to bind listener
2024-08-20T07:45:25.007362-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
2024-08-20T07:45:25.007386-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix
2024-08-20T07:45:25.017161-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777
2024-08-20T07:45:25.027261-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketCreateListener: failed to bind listener
2024-08-20T07:45:25.027309-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
2024-08-20T07:45:25.027330-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix
2024-08-20T07:45:25.037256-04:00 OPX3050 /usr/libexec/gdm-x-session[3395]: _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777

Permissions on .X11-unix seem fine:
jrm@OPX3050:~$ ll /tmp
total 72
drwxrwxrwt 15 root root 16384 2024-08-20 07:50 ./
drwxr-xr-x 23 root root 4096 2024-08-20 07:44 ../
drwxrwxrwt 2 root root 4096 2024-08-20 07:42 .ICE-unix/
drwxrwxrwx 2 root root 60 2024-08-20 07:42 .X11-unix/
drwxrwxrwt 2 root root 4096 2024-08-20 07:42 .XIM-unix/
drwxrwxrwt 2 root root 4096 2024-08-20 07:42 .font-unix/

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Fresh Win11 & Fresh WSL2 Ubuntu install, no X apps work, Xwayland process runaway (#9701), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[rye2020]

WslLogs-2024-08-20_09-43-55.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel found: 'C:\Users\jrmar\vmlinux'
Detected appx version: 2.3.17.0

[rye2020]

Turned off custom kernel. Same behavior.

WslLogs-2024-08-20_10-08-46.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.3.17.0

[elsaco]

Permissions on .X11-unix seem fine ...not quiet! /tmp/.X11-unix does not have the sticky bit set and your pmlogger is complaining about it. Currently it is set to drwxrwxrwx and your app expects drwxrwxrwt

[OneBlue]

/dupe #1122

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

[rye2020]

1. sudo chmod +t /tmp/.X11-unix is ineffective in setting the sticky bit
2. sometimes sudo mount -o remount,rw /tmp/.X11-unix will reset the sticky bit; it does not hold across reboots
3. I do not understand how gcc #1122 is related to this issue. Pardon my limited experience.

[jovere]

@OneBlue This has nothing to do with #1122 and it is filling the log making it entirely unusable.

[lvlte]

This is wslg#1122 actually, and there is a linked PR which has remained open without any news since Nov. 2023.

However, the steps to reproduce the issue here are not the same, and the consequences of having indefinitely growing logs is not addressed in the other issue. @OneBlue could you transfer this issue to wslg repo or reopen it ?

I also found #9303 , which is closed as completed without providing any fix.

There are literally GB of logs (syslog, journalctl, X.org) filled with this error. Remounting/chmoding /tmp/.X11-unix manually works but is not really a solution. And doing the same via systemd fix the error/log issue, but in my case the x11 socket vanishes and then WSLG crashes when I try to launch the same GUI apps that usually work with the error...