maxb commented 2 months ago

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Set guiApplications=false - it doesn't matter if you do this via %USERPROFILE%.wslconfig or /etc/wsl.conf

Start WSL afresh

Check what mounts exist with findmnt

Expected Behavior

Since WSLg is switched off, no mounts related to it should exist

Actual Behavior

Near the end of findmnt output:

│ └─/run/user                   none        tmpfs       rw,nosuid,nodev,noexec,noatime,mode=755
│   └─/run/user                 /dev/sdc[/mnt/wslg/run/user]
│                                           ext4        rw,relatime,discard,errors=remount-ro,data=ordered
│     └─/run/user/1000          tmpfs       tmpfs       rw,nosuid,nodev,relatime,size=795240k,nr_inodes=198810,mode=700,uid=1000,gid=1000

it can be seen (the middle two lines above) that /mnt/wslg/run/user has been mounted over /run/user even though WSLg is otherwise turned off.

Diagnostic Logs

No response

github-actions[bot] commented 2 months ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) 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!

Open similar issues:

mounting of /mnt/wslg as user runtime dir breaks all users except that with uid=1000 (#9025), similarity score: 0.72

Closed similar issues:

guiApplications=false causes broken systemd environment (#10818), similarity score: 0.80
WSL version 2.0.12 makes $XDG_RUNTIME_DIR not user accessible when guiApplications=false (#10846), similarity score: 0.76
[0.68.2] systemd user session destroys /mnt/wslg/runtime-dir (#8918), similarity score: 0.72

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

maxb commented 2 months ago

WslLogs-2024-08-18_14-59-30.zip

Frustrating to be made to jump through hoops attaching logs when I've already given a thorough reproduction recipe...