Error starting WT with egl_bindings.rs not getting loaded

[paulhocker]

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

Operating System: Kubuntu 25.10 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.2 Kernel Version: 6.17.0-6-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 32 GiB of RAM (31.3 GiB usable) Graphics Processor: AMD Radeon RX 6600 XT

WezTerm version

wezterm 20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

There was a recent update to KDE of which I guess there might have been mesa updates (not sure) but wezterm (and others like alacritty and kitty term) are all failing with this exact same error. I am sure this is not a bug with WT, but I was hoping to get more eyes on this to see how I might be able to recover. It has something to do with RUST, but I am just not versed enough to understand what.

Ghostty also had the same problem, but after I upgraded Kubuntu to 25.10 the problem went away.

09:02:50.226 ERROR env_bootstrap > panic at /__w/wezterm/wezterm/target/release/build/window-d36014842ac071d0/out/egl_bindings.rs:312:13 - egl function was not loaded 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 19: __libc_start_main_impl at ./csu/../csu/libc-start.c:360:3 20:

thread 'main' panicked at /__w/wezterm/wezterm/target/release/build/window-d36014842ac071d0/out/egl_bindings.rs:312:13: egl function was not loaded note: run with RUST_BACKTRACE=1 environment variable to display a backtrace warning: queue 0x5fe59f6634e0 destroyed while proxies still attached: xdg_wm_base#23 still attached wl_surface#22 still attached wl_data_device#19 still attached wl_pointer#17 still attached zwp_text_input_v3#16 still attached wl_keyboard#15 still attached zwp_primary_selection_device_v1#14 still attached zwp_primary_selection_device_manager_v1#3 still attached wl_data_device#13 still attached zwp_text_input_manager_v3#12 still attached wl_output#11 still attached wl_output#10 still attached wl_subcompositor#9 still attached wl_data_device_manager#8 still attached wl_seat#7 still attached wl_shm#6 still attached zxdg_decoration_manager_v1#5 still attached wl_compositor#4 still attached wl_registry#2 still attached

To Reproduce

Opening WT from menu does nothing.

Opening WT from console produces error listed above.

Configuration

-- Pull in the wezterm API local wezterm = require("wezterm")

-- This will hold the configuration. local config = wezterm.config_builder()

-- This is where you actually apply your config choices.

-- For example, changing the initial geometry for new windows: config.initial_cols = 120 config.initial_rows = 28

-- or, changing the font size and color scheme. config.font_size = 12 --config.color_scheme = "AdventureTime" --config.color_scheme = "Borland"

config.use_fancy_tab_bar = true config.enable_tab_bar = true

-- Finally, return the configuration to wezterm:

Expected Behavior

WT should open?

Logs

gui-sock-43211

cat: gui-sock-43211: Connection refused (os error 111)

wayland-wayland-0-org.wezfurlong.wezterm

cat: wayland-wayland-0-org.wezfurlong.wezterm: Connection refused (os error 111)

wezterm-gui-log-43211.txt

09:13:12.278 ERROR env_bootstrap > panic at /__w/wezterm/wezterm/target/release/build/window-d36014842ac071d0/out/egl_bindings.rs:312:13 - egl function was not loaded 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 19: __libc_start_main_impl at ./csu/../csu/libc-start.c:360:3 20:

Anything else?

Like I said, I really dont think this is a WZ bug, and I laso tried the nightly build. This is something that got broke on my systems and nothing is reported on KDE Bugs, so just hoping someone else had this same issue and knows how to fix it.

Thanks

[mberry]

Kubuntu 25.04 / Wayland / wezterm 20240203-110809-5046fc22 / apt install

Had to disable Wayland in the application launcher to get it working again.

~/.config/systemd/user/[email protected]/override.conf

[Service]
UnsetEnvironment=WAYLAND_DISPLAY

Then systemctl --user daemon-reload

---

Note that disabling wayland in WT config changed nothing

config.enable_wayland = false  -- Doesn't work

---

Maybe unrelated but this is my current application entry env vars which force gpu usage:

 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia

[avatar382]

I'm having the exact same issue (same stack trace as OP) on two different systems.

Both of my workstations are on fully up to date Kubuntu 25.04. It seems like a recent OS update broke Wezterm, as it was working on both a couple days ago.

One of my workstations is a Ryzen 7, with R780M integrated graphics. The other is an Intel i7-1250U with Intel Iris Xe integrated graphics.

Both of my systems are on X11, so this doesn't seem to be a Wayland specific issue.

To troubleshoot, I tried installing the latest nightly release, as well as adding config.front_end = "WebGpu" to my Wezterm config.

Neither of these worked and I'm not sure what to try next.

[IvayloHrTonev]

Same issue.

KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 128 GiB of RAM (125.7 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D54
System Version: 1.0```

wezterm --version      
wezterm 20251025-070338-b6e75fd7

Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 24 [Radeon RX 6400/6500
    XT/6500M] driver: amdgpu v: kernel
  Device-2: Generalplus Nacon PC Webcam driver: snd-usb-audio,uvcvideo
    type: USB
  Display: x11 server: X.Org v: 21.1.20 with: Xwayland v: 24.1.9 driver: X:
    loaded: amdgpu unloaded: modesetting,vesa dri: swrast gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 vendor: mesa v: 25.2.6-arch1.1 renderer: llvmpipe
    (LLVM 21.1.4 256 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top, corectrl, lact,
    radeontop wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr

Edit: Flatpack version works fine

[akocur]

Error: egl function was not loaded with NoMachine installed

Environment:

• OS: Debian 12 Bookworm
• Wezterm: Latest version from official repository (apt.fury.io)
• Graphics: AMD Raphael (Ryzen 7000 series) with integrated RDNA2 graphics
• Session: X11

Error:

13:33:23.111 ERROR env_bootstrap > panic at /_w/wezterm/wezterm/target/release/build/window-d36014842ac071d0/out/eglbindings.rs:312:13 - egl function was not loaded thread 'main' panicked at egl function was not loaded

Root Cause: Conflict with NoMachine (NX technology). NoMachine installs its own EGL libraries in /usr/NX/lib/ and configures LD_PRELOAD or LD_LIBRARY_PATH, which conflicts with system EGL libraries.

Diagnosis:

• Load logs show: calling init: /usr/NX/lib/libnxegl.so
• NoMachine intercepts EGL function calls
• After removing NoMachine, Wezterm works normally

Solution:

1. Remove NoMachine: sudo apt remove nomachine
2. Remove NoMachine files: sudo rm -rf /usr/NX/
3. Clear environment variables: unset LD_PRELOAD

Note: The issue occurs even when using X11 session, not just Wayland.

[avatar382]

@akocur Thanks for this, removing nomachine resolved the problems I was having launching Wezterm.