-
Notifications
You must be signed in to change notification settings - Fork 855
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
libEGL fatal: did not find extension DRI_Mesa version 1 when trying to run GUI apps #12581
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease 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:
Closed similar issues:
|
@the-alex-paterson Or use for a quick test:
and see if it launches okay. To get more info about your Mesa setup run |
The quick test didn't work. This is what I see when I run
|
Please check
This is the output of
Notice the device |
This is what I see when I enter
|
Exact same error on my Ubuntu machine since today (gnome-text-editor was definitely working fine yesterday/the day before), which may show that it's not a Windows specific bug :
|
I followed the instructions here and tried to install gnome-text-editor
When I try to run the command
gnome-text-editor ~/.bashrc
I'm getting this message in the terminallibEGL fatal: did not find extension DRI_Mesa version 1
I tried going through the troubleshooting page here but I'm still having issues.
At the bottom of that page are a list of commands that might be needed to help solve this.
weston.log
The text was updated successfully, but these errors were encountered: