Skip to content
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

Depth engine initialize failed on WSL2 #163

Open
Darth-S1d1ous opened this issue Feb 6, 2025 · 0 comments
Open

Depth engine initialize failed on WSL2 #163

Darth-S1d1ous opened this issue Feb 6, 2025 · 0 comments

Comments

@Darth-S1d1ous
Copy link

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:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant