Few seconds after starting things break

[LeonardoMor]

I use blesh on WSL2 with Arch Linux.

Whenever I turn on my computer and open an Arch CLI, things load and appear to be fine. Then after a few seconds, every key press results in this:

So there you can see I was in the middle of typing exit.

Then I have to close this Tab and open a new one. The second Tab doesn't do this and I can work normally. Not sure why this is happening. Help is appreciated.

[akinomyoga]

Exactly the same issue but for /run/user was reported in #426, and it turned out that WSL's /run/user is broken [1-7]. I added a workaround not to use /run/user in WSL.

• [1] WSLg's runtime-dir has always owner 1000 resulting in inaccessable runtime dir for default user microsoft/WSL#9689
• [2] /run/user/1000 owner become root when pre mount a vhdx disk before start the wsl system microsoft/WSL#10473
• [3] systemd_249.11-0ubuntu3.10 seems to break user sessions on WSL2 microsoft/WSL#10496
• [4] mkdir /run/user/1000/: permission denied after WSL 2.0.0 microsoft/WSL#10498
• [5] WSL 2.0.1: systemd-logind logs session out after few minutes, purges /run/user/{uid} microsoft/WSL#10552
• [6] WSLでsystemctl status --userがNo such file or directoryになる / Failed to connect to a Wayland serverとなってWalyandにつながらない - ぶていのログでぶログ
• [7] Nvim always logs server_start:164 error in WSL (SOLVED: permissions issue) · Issue #26058 · neovim/neovim

Maybe /tmp is also broken in WSL.

[akinomyoga]

Hmm, according to microsoft/WSL#8441 (comment), the contents of /tmp seem to be cleared after a few seconds since the WSL system boots up. This is consistent with your observation. The problem doesn't seem to be fixed because the issue was just closed, and there is no mention after that. Maybe I need to avoid using even /tmp in WSL.

[akinomyoga]

microsoft/WSL#8441 (comment) says that a new issue for WSL should be created if the problem persists. I thought about creating an issue, but they require the version information of Windows, WSL, Linux kernel, Distro, etc. I don't have detailed information about your environment. @LeonardoMor Could you create an issue at WSL? I think you can use microsoft/WSL#8441 as a template. You can also include mentions of microsoft/WSL#8441, this discussion, etc.

[akinomyoga]

I added a workaround in fcbf1ed. You can update ble.sh by running ble-update and see if the problem is solved. (If you use v0.3 of ble.sh, please switch to 0.4.)

@LeonardoMor Have you created an issue in the upstream WSL repository? If not, maybe I can create one if you could provide the version information of Windows, WSL, Linux kernel, Distro in your environment.

[LeonardoMor]

Created issue 11739

[akinomyoga]

Thank you!