Open MikuAuahDark opened 1 year ago
Forgot to attach WSL logs from powershell. WslLogs-2023-04-15_22-47-06.zip
I've been running into a similar sort of problem, where OpenGL seems to cause a segfault somewhere deep in the gears of the graphics driver. I'm fairly confident this is a WSL problem, as attempting to run the same code in Windows works fine. I can't offer any direct reproduction code publicly, since I'm encountering it while trying to work on a class assignment, but it seems to be emerging primarily whenever I start trying to interact with texture data in shaders. I tried to upgrade to a newer version of mesa as specified in a different issue, but no dice.
This is probably pretty implementation-dependent, but I am at least able to consistently get code that works and code that doesn't by negating a vec3 in a simple phong shader in GLSL, storing the new negated value in a vector and attempting to later use it.
WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1555
glxinfo -B
:
@MikuAuahDark, what version of AMD GPU driver is used in Windows side?
@lewcc, would you please share your GPU driver in Windows?
Thanks!
It's still a driver from OEM and the drivers hasn't been updated since August 2021.
For my case, it used to work. Unfortunately I'm unable to pinpoint exactly when this start happening other than since my bug report.
EDIT: Updated WSL to 1.2.5.0 and Windows to build 1635, still same segfault.
It used to work for me a few months ago too
I ended up just using this workaround: LIBGL_ALWAYS_SOFTWARE=1 glxgears
It used to work for me a few months ago too
I ended up just using this workaround:
LIBGL_ALWAYS_SOFTWARE=1 glxgears
It works for me, too !!! (I have searched for the solution for hours...) Thanks very much.
I ended up set 'export LIBGL_ALWAYS_SOFTWARE=1' in '~/.bashrc' . And everything worked.
LIBGL_ALWAYS_SOFTWARE=1
means you're not using the GPU at all.
Also getting this problem on AMD. DXDiag below:
I resolved this by entering an elevated command prompt and running wsl --update
.
Windows build number:
22621.1555
Your Distribution version:
Debian GNU/Linux 12 (bookworm)
Your WSL versions:
WSL version: 1.2.0.0 Kernel version: 5.15.90.1 WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22621.1555
Steps to reproduce:
Simply run
glxgears
.WSL logs:
pulseaudio.log weston.log stderr.log
WSL dumps:
No files in
/mnt/wslg/dumps
.Expected behavior:
Gears shown, which was the case few months ago.
Actual behavior:
Segmentation fault.
Backtrace of running through GDB with debuginfod.
glxinfo -B
output: