search

microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
10.26k stars 310 forks source link

MESA ERROR #1283

Open Perdixky opened 2 months ago

Perdixky commented 2 months ago

Windows Version

Microsoft Windows [version 10.0.26120.1542]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

Kernel Version

6.6.36.6

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

When I use the GUI, I usually see error messages related to rendering, but they don't generally affect usage:

> gz sim
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3070)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization
> emacs
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3070)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization

However, recently when using gnome-font-viewer, I encountered the following:

libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI3: Screen seems not DRI3 capable
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3070)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization
MESA: error: Failed to attach to x11 shm

It displays a transparent box, making it unusable.

Expected Behavior

I hope there is a solution to open gnome-font-viewer. In fact, I don't really understand graphic rendering and am not sure whether the problem lies with OPENGL, MESA, dzn, or Vulkan.

Actual Behavior

MESA: error: Failed to attach to x11 shm

Diagnostic Logs

No response

github-actions[bot] commented 2 months ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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'.
Perdixky commented 2 months ago

WslLogs-2024-09-08_15-52-03.zip

github-actions[bot] commented 2 months ago
Diagnostic information ``` .wslconfig found Custom kernel found: 'C:\Windows\System32\lxss\tools\kernel' Detected appx version: 2.2.4.0 ```
Perdixky commented 2 months ago

Diagnostic information

.wslconfig found
  Custom kernel found: 'C:\Windows\System32\lxss\tools\kernel'
Detected appx version: 2.2.4.0

The kernel was compiled and installed by me using the kernel from https://github.com/microsoft/WSL2-Linux-Kernel. Detailed version information:

commit e458890574d4b6d635880180ef9e5d2b621ff577 (HEAD -> linux-msft-wsl-6.6.y, tag: linux-msft-wsl-6.6.36.6, origin/linux-msft-wsl-6.6.y, origin/HEAD)
Merge: 149cbd13f7c0 6cb123f853df
Author: Mitchell Levy <levymitchell0@gmail.com>
Date:   Tue Sep 3 14:23:23 2024 -0700

    Merge tag 'rolling-lts/wsl/6.6.36.6' into linux-msft-wsl-6.6.y

    Linux rolling-lts/wsl/6.6.36.6

    Signed-off-by: Mitchell Levy <levymitchell0@gmail.com>
uureel commented 2 months ago

don't run wslg stuff as root

Perdixky commented 2 months ago

don't run wslg stuff as root

Thank you for your suggestion! However, I am not using the root account. The problem is still there

uureel commented 2 months ago

don't run wslg stuff as root

Thank you for your suggestion! However, I am not using the root account. The problem is still there

try ln -sf /mnt/wslg/runtime-dir/wayland* /run/user/0/ dbus-run-session gnome-font-viewer

Perdixky commented 2 months ago

don't run wslg stuff as root

Thank you for your suggestion! However, I am not using the root account. The problem is still there

try ln -sf /mnt/wslg/runtime-dir/wayland* /run/user/0/ dbus-run-session gnome-font-viewer

I have only one folder named 1002 under my /run/user directory, so I used the following command:

> noglob sudo ln -sf /mnt/wslg/runtime-dir/wayland* /run/user/1002/
> dbus-run-session gnome-font-viewer

However, the following error was still thrown:

libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI3: Screen seems not DRI3 capable
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3070)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization
dbus-daemon[1149]: [session uid=0 pid=1149] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=1150 comm="gnome-font-viewer" label="kernel")
dbus-daemon[1149]: [session uid=0 pid=1149] Successfully activated service 'org.a11y.Bus'
MESA: error: Failed to attach to x11 shm
dbus-daemon[1183]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=1150 comm="gnome-font-viewer" label="kernel")
dbus-daemon[1183]: Successfully activated service 'org.a11y.atspi.Registry'
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
MESA: error: Failed to attach to x11 shm
ACGNnsj commented 1 month ago

don't run wslg stuff as root

Thank you for your suggestion! However, I am not using the root account. The problem is still there

try ln -sf /mnt/wslg/runtime-dir/wayland* /run/user/0/ dbus-run-session gnome-font-viewer

Thanks. It seems to work for me.

skemo12 commented 1 month ago

Any updates on this ? I am getting this warning on python3 matlib plot.

WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3070 Ti)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterizatio
tms320 commented 1 week ago

The same warnings (without errors):

WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce GTX 1050 Ti)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization