Screen sharing crashes

[Unfinished632]

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.

• 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).

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

• 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

33.3.1

Application version

v4.10.3

Bug description

Whenever I try to screen share it waits a second and then crashes. I don't know exactly when this started happening since I don't share screen very often but I do know that it used to work fine.

Output:

MESA-LOADER: failed to open nvidia: /usr/lib/gbm/nvidia_gbm.so: cannot open shared object file: No such file or directory (search paths /usr/lib/gbm, suffix _gbm)
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

[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()
Segmentation fault (core dumped)

Additional context

Im using Wayland.

Im sure that it's not a problem with my desktop portal since i can still record on OBS.

[SpacingBat3]

What distributable (deb,pkg.*,AppImage etc.) are you using to reproduce this issue?

[Unfinished632]

I'm using this AUR package: https://aur.archlinux.org/packages/webcord

[Sycration]

Same issue here, with the same package

I'm using this AUR package: https://aur.archlinux.org/packages/webcord

[levdev0]

I have the exact same issue please let me know if anybody knows a fix for this

[szabatoro]

Same here using the AUR package

[szabatoro]

Same here using the AUR package

Happens with the appimage on the github release as well. Terminal output:

[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()
xargs: /tmp/.mount_WebCorGaCkOf/usr/lib/webcord/webcord: terminated by signal 11