$HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper failed

Support Graphics & Display
1

At every boot, I get the following error report. No consequence seem to appear, but I still investigated

Bug report

           PID: 4209 (gpu_encoder_hel)
           UID: 1000 (me)
           GID: 1000 (me)
        Signal: 11 (SEGV)
     Timestamp: Mon 2026-04-13 20:35:37 CEST (18s ago)
  Command Line: $HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper intel
    Executable: $HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-discord@autostart.service
          Unit: user@1000.service
     User Unit: app-discord@autostart.service
         Slice: user-1000.slice
     Owner UID: 1000 (me)
       Boot ID: <>
    Machine ID: <>
      Hostname: <>
       Storage: /var/lib/systemd/coredump/core.gpu_encoder_hel.1000.5a552f465b0c457cbaddd3878575fb47.4209.1776105337000000.zst (present)
  Size on Disk: 119.2K
       Message: Process 4209 (gpu_encoder_hel) of user 1000 dumped core.
                
                Module $HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper without build-id.
                Stack trace of thread 4209:
                #0  0x00007fa661f55864 XDisplayString (libX11.so.6 + 0x27864)
                #1  0x00007fa662ae1d00 __vaDriverInit_1_21 (nvidia_drv_video.so + 0xdd00)
                #2  0x00007fa662d1ed9d vaInitialize (libva.so.2 + 0xbd9d)
                #3  0x00005560262a2502 _ZN10cros_libva7display7Display16open_drm_display17hd5d46350d44da865E ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x34502)
                #4  0x00005560262a269c _ZN20vaapi_media_encoding5probe22probe_vaapi_for_vendor17hacc3a6ae8c53a57fE ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x3469c)
                #5  0x00005560262a25d0 _ZN100_$LT$vaapi_media_encoding..probe..IntelEncoderProbe$u20$as$u20$media_encoding..gpu..EncoderProbe$GT$5probe17hd7c63c390a0503acE ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x345d0)
                #6  0x000055602629cd63 _ZN18gpu_encoder_helper5linux3run17h25db6ea530f7b70aE ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x2ed63)
                #7  0x000055602629f9e3 _ZN3std3sys9backtrace28__rust_begin_short_backtrace17h4194352c86d676e3E ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x319e3)
                #8  0x000055602629fe59 _ZN3std2rt10lang_start28_$u7b$$u7b$closure$u7d$$u7d$17hcf4b259b4d45cf53E.llvm.126661360784045746 ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x31e59)
                #9  0x00005560262f484a _ZN3std2rt19lang_start_internal17h47f73bfd01f1f70bE ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x8684a)
                #10 0x000055602629fa25 main ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x31a25)
                #11 0x00007fa662b127f9 __libc_start_main (libc.so.6 + 0x277f9)
                #12 0x000055602629924a _start ($HOME/.config/discord/0.0.132/modules/discord_voice/gpu_encoder_helper + 0x2b24a)
                ELF object binary architecture: AMD x86-64

Using gdb, I found that __vaDriverInit_1_21 gets called with this:

*ctx = {pDriverData = 0x0, vtable = 0x55555564da20, vtable_glx = 0x0, vtable_egl = 0x0, vtable_tpi = 0x0, native_dpy = 0x0, x11_screen = 0, version_major = 0, version_minor = 0, max_profiles = 0, max_entrypoints = 0, 
  max_attributes = 0, max_image_formats = 0, max_subpic_formats = 0, max_display_attributes = 0, str_vendor = 0x0, handle = 0x0, drm_state = 0x555555648490, glx = 0x0, display_type = 49, vtable_wayland = 0x0, 
  vtable_vpp = 0x55555564ce70, override_driver_name = 0x0, pDisplayContext = 0x5555556484c0, error_callback = 0x7ffff7f7f140 <va_driverErrorCallback>, info_callback = 0x7ffff7f7f170 <va_driverInfoCallback>, 
  vtable_prot = 0x55555564de60, reserved = {0 <repeats 37 times>}}

and then, as shown in the backtrace, XDisplayString gets called with dpy = \0 and this results in a SEGFAULT.

2

A proprietary app :poop: which is constantly changed. Pretty much always in alpha quality state…

Sorry for the hate. But why the FOSS community should fix bugs in a property software…

That said i hope somebody can assist you.

3

It’s not immediately clear to me whether the bug is on Discord or on nvidia drivers. I guess I can report this to Discord and see what happens.

1 Like
4

I had that problem with Avidemux. VAAPI tried unsuccessfully (on my all-AMD system) to load nvidia_drv_video.so.

Have you tried running Discord with LIBVA_DRIVER_NAME=none discord or whatever command is used to launch Discord from the shell?

I hope I’m remembering the variable correctly…

EDIT: Also have a look at 3.1

1 Like
5

Probably related: LIBVA_DRIVER_NAME=nvidia vainfo raises floating point exception (core dumped)