Screen sharing crashes WebCord on Arch Linux (Hyprland): GL initialization & Pipewire errors

[levdev0]

Acknowledgements

• I have checked that there is no other issue describing the same or
  similar problem that I currently have, regardless if it has been
  closed or open.

• This bug affects Discord website.

• This issue is confirmed to be reproducible when WebCord is packaged
  on at least all three latest supported Electron major releases.

• There are no fixes done to master which resolves this issue.

• This issue is reproducible in Chrome, Chromium or any
  Chromium-based browser, e.g Brave or Edge (please write in
  Additional Context which browser you have used if it is neither
  Chrome nor unmodified Chromium).

• My issue describes one of the unstable and/or not fully implemented
  features.

• I have found a workaround to mitigate or temporarily fix this issue
  in affected releases (please write it in Additional context section
  below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

v33.4.1

Application version

WebCord v4.10.3, stable build

Bug description

Description:

When attempting to share my screen on Arch Linux running Hyprland, WebCord immediately crashes. In addition, file uploads are failing. Below are the details of the screen share crash.

System Information:

OS: Arch Linux
Window Manager/Compositor: Hyprland
WebCord Version: v4.10.3
GPU: Nvidia RTX4060
Installation Method: AUR
Additional Logs/Notes:
    The error indicates that the GL implementation requested (egl-gles2,angle=none) is not among the allowed implementations.
    The Pipewire error (loop->recurse > 0 failed) suggests there might be an issue with Pipewire's thread loop management during screen sharing.

it ran under the xwayland protocol

Log:

[436321:0217/225106.297806:ERROR:gl_factory.cc(102)] Requested GL implementation (gl=egl-gles2,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=opengl),(gl=egl-angle,angle=opengles),(gl=egl-angle,angle=vulkan),(gl=egl-angle,angle=swiftshader)].
[436321:0217/225106.298527:ERROR:viz_main_impl.cc(181)] Exiting GPU process due to errors during initialization
[436348:0217/225106.421191:ERROR:gl_factory.cc(102)] Requested GL implementation (gl=egl-gles2,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=opengl),(gl=egl-angle,angle=opengles),(gl=egl-angle,angle=vulkan),(gl=egl-angle,angle=swiftshader)].
[436348:0217/225106.421976:ERROR:viz_main_impl.cc(181)] Exiting GPU process due to errors during initialization
[436359:0217/225106.441841:ERROR:gl_factory.cc(102)] Requested GL implementation (gl=egl-gles2,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=opengl),(gl=egl-angle,angle=opengles),(gl=egl-angle,angle=vulkan),(gl=egl-angle,angle=swiftshader)].
[436359:0217/225106.442531:ERROR:viz_main_impl.cc(181)] Exiting GPU process due to errors during initialization
[WebSocket] Listening at port 6463.
[UPDATE] Application is up-to-date!
'loop->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
[1] 436282 segmentation fault (core dumped) webcord

Additional context

It appears that WebCord is attempting to initialize a GL implementation that your system does not support, which causes the GPU process to exit and ultimately leads to a segmentation fault. This might be a configuration issue with WebCord’s GPU/GL settings or a compatibility problem with Pipewire on Hyprland. Testing with a different GL flag (e.g., forcing egl-angle if possible) or checking for updates to Pipewire and your GPU drivers might provide a temporary workaround.

What might be the issue?

Based on the logs, it looks like WebCord is requesting a GL implementation (egl-gles2,angle=none) that isn’t available in your system’s allowed list. This mismatch causes the GPU process to fail, leading to a crash during screen sharing. The Pipewire thread loop error further suggests that this failure might be affecting other subsystems (like Pipewire) responsible for handling screen capture or sharing. It’s possible that a configuration or compatibility issue between WebCord, your GPU drivers, and Pipewire on Hyprland is causing these crashes.

Any guidance or suggestions for workarounds (such as using a different GL flag or updating relevant packages) would be greatly appreciated.

[SpacingBat3]

Any guidance or suggestions for workarounds (such as using a different GL flag or updating relevant packages) would be greatly appreciated.

Try different Electron versions, different PipeWire protocol implementations and check whenever you're software decoding or hardware decoding.

When it comes to Electron+Wayland, it's hit-or-miss adventure, I feel like it greatly matters on the software you're using (drivers most likely), particular Electron build and sometimes on some configuration factors (I had once issue caused by basically my XDG protocol implementation provider's service being dead and I had to enable it via systemd CLI). A lot of stuff is actually reproducible in Chromium as well.

I suppose on Arch running WebCord with different Electron version is as easy as installing different electron package version and running:

electron /path/to/app.asar

You can get actual path to app.asar using pacman -Ql webcord or something like that.

I might go with releasing an update with dependency bumps for starters on my side. Given you're actually using updated Electron version, it's rather not going to help, but still that's something I could do finally.

[din-grogu]

Any guidance or suggestions for workarounds (such as using a different GL flag or updating relevant packages) would be greatly appreciated.

Try different Electron versions, different PipeWire protocol implementations and check whenever you're software decoding or hardware decoding.

When it comes to Electron+Wayland, it's hit-or-miss adventure, I feel like it greatly matters on the software you're using (drivers most likely), particular Electron build and sometimes on some configuration factors (I had once issue caused by basically my XDG protocol implementation provider's service being dead and I had to enable it via systemd CLI). A lot of stuff is actually reproducible in Chromium as well.

I suppose on Arch running WebCord with different Electron version is as easy as installing different electron package version and running:

electron /path/to/app.asar

You can get actual path to app.asar using pacman -Ql webcord or something like that.

I might go with releasing an update with dependency bumps for starters on my side. Given you're actually using updated Electron version, it's rather not going to help, but still that's something I could do finally.

Also on Arch and Hyprland. Had the same issue, now using Electron version 31, I've tried

$ electron31 /opt/webcord/resources/app.asar

and can confirm it now works, just add the line in the webcord.desktop file afterwards and it should work as a fix.

Didn't try other versions though. Thanks for the quick fix!

[David-Kopczynski]

For me electron with version 32.3.1 also works fine! The issue seems to begin with version 33

[0xIO32]

I can reproduce with electron 34.4.1 and native wayland (no xwayland being used, also hyprland btw).

[huyhoang8398]

same with electron 35, archlinux + native wayland hyprland

[0xIO32]

Can anyone test if this is a hyprland only issue? Haven't seen people here with other desktops

[samken600]

I am also using Hyprland. I can contribute the verbose log snippet from the crash:

libEGL warning: egl: failed to create dri2 screen
MESA: error: ZINK: vkEnumeratePhysicalDevices failed (VK_ERROR_INITIALIZATION_FAILED)
MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
[API] Blocking /api/v9/science
'loop->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
Segmentation fault (core dumped)

My system details:

OS: Arch Linux x86_64
Host: MS-7C37 1.0
Kernel: 6.14.2-arch1-1
DE: Hyprland
CPU: AMD Ryzen 7 3800X (16) @ 4.560GHz
GPU: NVIDIA GeForce RTX 2070 SUPER
Memory: 2567MiB / 32009MiB

I am running the v4.10.5 AppImage release with Electron 35.2.0, Chromium 134.0.6998.205, and Node 22.14.0.

I haven't tried with other Electron versions yet. I am not sure when this started breaking as I updated quite a few versions and had not tried screen sharing in a while, but I know that it used to work on my setup.

[David-Kopczynski]

Can anyone test if this is a hyprland only issue? Haven't seen people here with other desktops

I am using NixOS with GNOME. I opened a issue here with more information: NixOS/nixpkgs#385588

[Nekiker]

/usr/lib/electron31/electron "/usr/lib/webcord"

For those who don't have app.asar . I installed webcord from AUR (Arch Linux).

[andradei]

Can anyone test if this is a hyprland only issue? Haven't seen people here with other desktops

The same issue with the same pipewire errors on niri.

The temporary fix also worked on arch:

yay -S electron32
electron32 /opt/webcord/resources/app.asar