# EGL issues when connecting to ZEDX

**URL:** <https://community.stereolabs.com/t/egl-issues-when-connecting-to-zedx/11183>\
**Category:** ZED X\
**Created:** [April 15, 2026, 5:12am UTC](https://community.stereolabs.com/t/egl-issues-when-connecting-to-zedx/11183 "2026-04-15T05:12:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![samfreund](https://community.stereolabs.com/user_avatar/community.stereolabs.com/samfreund/32/5114_2.png) [@samfreund](https://community.stereolabs.com/u/samfreund)\
**Post date:** [April 15, 2026, 5:12am UTC](https://community.stereolabs.com/t/egl-issues-when-connecting-to-zedx/11183/1 "2026-04-15T05:12:05Z")

</div>

When attempting to run ZED\_Explorer, I’m hitting an issue with EGL.

```auto
USER@ubuntu ~ [SIGABRT]> ZED_Explorer
 **[SVO] Hardware compression (NVENC) available**
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
(Argus) Error BadParameter: (propagating from src/common/ScopedNvGlsiEglImageRef.cpp, function reset(), line 39)
(Argus) Error BadParameter: (propagating from src/rpc/socket/client/CustomMethods.cpp, function createBuffer(), line 524)
Stack trace (most recent call last):
#22 Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in 
#21 Object "ZED_Explorer", at 0x45f8af, in 
#20 Object "/lib/aarch64-linux-gnu/libc.so.6", at 0xffffa52474d7, in __libc_start_main
#19 Object "/lib/aarch64-linux-gnu/libc.so.6", at 0xffffa52473ff, in 
#18 Object "ZED_Explorer", at 0x43752f, in 
#17 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa59741cb, in QCoreApplication::exec()
#16 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa596b06b, in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
#15 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa59cb523, in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
#14 Object "/lib/aarch64-linux-gnu/libglib-2.0.so.0", at 0xffffa38d3413, in g_main_context_iteration
#13 Object "/lib/aarch64-linux-gnu/libglib-2.0.so.0", at 0xffffa392cf9f, in 
#12 Object "/lib/aarch64-linux-gnu/libglib-2.0.so.0", at 0xffffa38d5fa7, in g_main_context_dispatch
#11 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa59cb1ab, in 
#10 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa59ca7e3, in QTimerInfoList::activateTimers()
#9 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa596cb8f, in QCoreApplication::notifyInternal2(QObject*, QEvent*)
#8 Object "/lib/aarch64-linux-gnu/libQt5Widgets.so.5", at 0xffffaa9f2abf, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#7 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa599cecf, in QObject::event(QEvent*)
#6 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa59ac00f, in QTimer::timeout(QTimer::QPrivateSignal)
#5 Object "/lib/aarch64-linux-gnu/libQt5Core.so.5", at 0xffffa59a7913, in 
#4 Object "ZED_Explorer", at 0x4b579b, in 
#3 Object "ZED_Explorer", at 0x4b4ca3, in 
#2 Object "ZED_Explorer", at 0x4b7743, in 
#1 Object "ZED_Explorer", at 0x5f2e13, in 
#0 Object "ZED_Explorer", at 0x5c2754, in 
Segmentation fault (Address not mapped to object [(nil)])
fish: Job 1, 'ZED_Explorer' terminated by signal SIGSEGV (Address boundary error)
USER@ubuntu ~ [SIGSEGV]> 

```

I’m using a Zed X camera connected to a Zed Link Duo, running on an AGX Orin. I’m running jetpack release 6.2.2, with the 1.4.1 ZEDX driver and ZED SDK 5.2

Running `ZEDX_Diagnostics` results in a similar error, although the checks with the `–dmesg` flag pass.

```auto

USER@ubuntu ~> ZED_Diagnostic 
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
nvbufsurface: Failed to create EGLImage.
(Argus) Error BadParameter: (propagating from src/common/ScopedNvGlsiEglImageRef.cpp, function reset(), line 39)
(Argus) Error BadParameter: (propagating from src/rpc/socket/client/CustomMethods.cpp, function createBuffer(), line 524)
Stack trace (most recent call last) in thread 2924:
#9 Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in 
#8 Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff97039e9b, in 
#7 Object "/usr/lib/aarch64-linux-gnu/libc.so.6", at 0xffff96fd0397, in 
#6 Object "/usr/lib/aarch64-linux-gnu/libstdc++.so.6", at 0xffff972a29cb, in 
#5 Object "ZED_Diagnostic", at 0x45a07f, in 
#4 Object "ZED_Diagnostic", at 0x4785d7, in 
#3 Object "ZED_Diagnostic", at 0x4780df, in 
#2 Object "ZED_Diagnostic", at 0x46e6e7, in 
#1 Object "ZED_Diagnostic", at 0x595a33, in 
#0 Object "ZED_Diagnostic", at 0x5654d4, in 
Segmentation fault (Address not mapped to object [(nil)])
fish: Job 1, 'ZED_Diagnostic' terminated by signal SIGSEGV (Address boundary error)
USER@ubuntu ~ [SIGSEGV]> ZED_Diagnostic --dmesg

 **Please wait for completion... This might take up to 1 minute**
- Running GMSL DRIVER Diagnostic : OK  
- Running Log Kernel Trace (for ZED X) Diagnostic : OK  

```

Running via CLI gives me this information before it crashes.

```auto
USER@ubuntu ~> ZED_Diagnostic -c
ZED Diagnostic Tool

- Running ZED SDK Diagnostic : OK  
    ZED SDK version: 5.2.3
    CUDA version: V12.6.68
- Running Processor Diagnostic : OK  
    Processor: ARMv8 Processor rev 1 (v8l)
    Motherboard: Jetson, NVIDIA
- Running Graphics Card Diagnostic : OK  
    Graphics card: Orin
- Running CUDA Operations Diagnostic : OK  
    GPU 0 (Orin): CUDA operations working correctly
- Running AI Models Diagnostic : OK  
    MULTI CLASS DETECTION is optimized
    MULTI CLASS MEDIUM DETECTION is optimized
    MULTI CLASS ACCURATE DETECTION is optimized
    HUMAN BODY FAST DETECTION is optimized
    HUMAN BODY MEDIUM DETECTION is optimized
    HUMAN BODY ACCURATE DETECTION is optimized
    HUMAN BODY 38 FAST DETECTION is optimized
    HUMAN BODY 38 MEDIUM DETECTION is optimized
    HUMAN BODY 38 ACCURATE DETECTION is optimized
    PERSON HEAD DETECTION is optimized
    PERSON HEAD ACCURATE DETECTION is optimized
    REID ASSOCIATION is optimized
    NEURAL LIGHT DEPTH is optimized
    NEURAL DEPTH is optimized
    NEURAL PLUS DEPTH is optimized

```

I’ve seen some information in prior posts about needing a dummy HDMI plug, but I’m guessing that since I’m able to get a noVNC instance up and running, and connect and see the applications before this error is hit, that isn’t the case.

---

<div class="post-metadata">

**Author:** ![BenjaminV](https://community.stereolabs.com/user_avatar/community.stereolabs.com/benjaminv/32/3863_2.png) [@BenjaminV](https://community.stereolabs.com/u/BenjaminV)\
**Post date:** [April 15, 2026, 6:52am UTC](https://community.stereolabs.com/t/egl-issues-when-connecting-to-zedx/11183/2 "2026-04-15T06:52:38Z")

</div>

Hi,

You indeed need to have a monitor plugged to your zed box in order to run opengl application (or have a dummy hdmi dongle).

You can also follow this guide to setup a virtual display on your Jetson :

> **[Using the ZED SDK with a Virtual Display on NVIDIA® Jetson™ - Stereolabs](https://www.stereolabs.com/docs/development/zed-sdk/virtual-display)**
>
> When working with a ZED camera and a ZED SDK-based application running on a remote NVIDIA® Jetson™ device, you may need to access the display output without physically connecting a monitor (headless …
