GUI Apps not starting: MESA: error: ZINK: failed to choose pdev

[Rhyzhang]

Just reposting this as issue from chris-neub

Discussed in #12243

^{Originally posted by chris-neub November 6, 2024}
Hi,

Infos:

WSL-Version: 2.3.24.0
Kernelversion: 5.15.153.1-2
WSLg-Version: 1.0.65
MSRDC-Version: 1.2.5620
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26100.1-240331-1435.ge-release
Windows-Version: 10.0.22631.4317

WSLg ( x86_64 ): 1.0.65+Branch.main.Sha.25d8697d5049e1994baa6ba542f507347b608ad4
Built at: Wed Aug 14 21:11:14 UTC 2024
Mariner: VERSION="2.0.20240609"
DirectX-Headers:
mesa:
pulseaudio: 6f045ff0dca233a939a2aba815f84d177e294122
FreeRDP: c4030980b29322a9cb2190711a5fadeeeb8b6a33
weston: f227edd681479ec3cb2290a25d84d2d3462aebfa

drwxrwxrwx  2 root      root        60 Nov  6 12:05 .
drwxrwxrwt 14 root      root      4096 Nov  6 12:06 ..
srwxrwxrwx  1 mindberry mindberry    0 Nov  6 12:05 X0

I'm very new to WSL and not a very good Linux User, but want to start with it. I've installed WSL according to windows learn and updated and upgraded it. However when I want to open an GUI like nautilus I always get this errors and it will open after a while:

** Message: 12:01:54.893: Connecting to org.freedesktop.Tracker3.Miner.Files
MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen

I've tried also to change the graphics adapter from Intel to Nvidia - but no difference. Drivers should be installed properly. I also have the same issues with an AMD notebook. So what do I miss?

[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 [email protected] 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:

• MESA ERROR (#12001), similarity score: 0.72

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

[Rhyzhang]

Previously, I was running the default Ubuntu (first point of release) on WSL2 and was running into this issue.

I uninstalled that distro and installed Ubuntu 22.04.5 LTS from microsoft store. I am not sure if it is the Ubuntu version change that did the trick or installing from Microsoft Store that did the trick. Anyways, I'm not having this issue anymore.