-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some files in /mnt appear only 2 bytes long => flurry of errors in /mnt/wslg/stderr.log #9261
Comments
|
It seems that WSL cannot parse this kind of reparse point. |
Apparently WSLg is trying to open a remote destop connection, but the file wslg.rdp looks incomplete:
This command from a CMD console opens a small window [RemoteApp] "Starting your app" that never connects.
|
@colemar the issue is not the reparsing. If you look at the output when you run
In my case is version 1.0.0. Looks like you're on version 1.0.3 already. |
Wait, on my system /mnt/wslg/stderr.log refers to and
Now in CMD.EXE
It seems to me that WSL sees the reparse point as a file of 2 bytes size containing only "MZ", while Windows understands the reparse point (at least when launching the process msrdc.exe). |
And it seems strange for WSL to refer to |
I see the same symptoms as @colemar describes on this box,
Using either Debian or Alpine (both installed via the MS Store),
When I run a X11 application such as xeyes, the app runs, but the window never appears. |
In Linux
And This is what Linux shell sees, and interop should take care of it:
If you use
and it's okay, too, because The issue you're having is with WSLg not working properly. |
There is no
which is supposed to work with PS Core 7.3.0. |
@elsaco Now WSL is able to start msrdc.exe via the reparse point:
If I remember well, version 1.0.3.0 was not able to start it. I am reinstalling this version to confirm. |
I unistalled WSL 1.0.0.0 and installed WSL 1.0.3.0 (via Appx package). WSL 1.0.3.0 is also able to start the reparse point, and I don't see anymore the original problem about /mnt/wslg/stderr.log. I see other issues in stderr.log, but I suppose these are not relevant:
|
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Windows version: 10.0.19045.2311
WSL Version
Kernel Version
5.15.79.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Install Ubuntu 22.04 via .appx package from https://aka.ms/wslubuntu2204 (or perhaps wsl --install Ubuntu).
Enable systemd.
Open elevated CMD.EXE
Expected Behavior
No errors in /mnt/wslg/stderr.log.
Good symbolic links in C:\Users\colem\AppData\Local\Microsoft\WindowsApps\
Actual Behavior
See Repro Steps.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: