OrbbecSDK icon indicating copy to clipboard operation
OrbbecSDK copied to clipboard

Depth engine initialize failed on WSL2

Open Darth-S1d1ous opened this issue 10 months ago • 0 comments

Describe the bug
I used usbipd to map the Femto Bolt device connected to Windows into WSL. When I tried to test the camera connection using OrbbecViewer, the color image stream displayed normally. However, as soon as I attempted to switch to the depth image stream, the viewer crashed and an error was reported. (this is not a problem of OrbbecViewer)

Reproduction Steps
On Windows: usbipd bind --busid usbipd attach --wsl --busid

On WSL2 Ubuntu22.04: sudo -i ./OrbbecViewer Then click on the "Depth" button on the top toolbar

Expected behavior
Depth engine initializes successfully and properly displays the depth image

Log Output
The following is the last normal output before I click on the button and the viewer crashes:

Image

Output of terminal:

Image

Output of eglinfo:

Image

System Environment:

  • OS: Windows11 with wsl2 Ubuntu22.04
  • Architecture: x86_64
  • Kernel: recompiled as prescribed by https://github.com/PINTO0309/wsl2_linux_kernel_usbcam_enable_conf/blob/main/linux-msft-wsl-5.15.90.1/config-Ubuntu-22.04

Tool/SDK Version:

  • SDK: Version v1.10.18
  • OrbbecViewer: v2.1.1

Device Information:

  • Model: Femto Bolt
  • Firmware Version: v1.0.9

Additional context
I suspect the issue might be related to WSL2's inability to communicate with the GPU. However, even after reinstalling the graphics driver and mesa-utils, the same error persists, and the dri/ directory still does not exist.

Darth-S1d1ous avatar Feb 06 '25 08:02 Darth-S1d1ous