I am running a system using Wayland (with Sway as the compositor) and `-X` in `/etc/make.conf`.
On that system, I was able to emerge media-video/obs-studio (after unmasking it ~amd64, to be fair), but it segfaults on start.
I am assuming this is due to lack of Wayland support in media-video/obs-studio-26.1.2 since https://github.com/obsproject/obs-studio/pull/2482 list the corresponding PR for Milestone 27.0.
I also found https://bugs.gentoo.org/770970 aiming to add the respective USE flag
to the -9999 ebuild, so I assume there is no need for a trace to figure out what exactly caused the segfault.
I still think of this as a packaging bug: If OBS (as of now) requires X11, portage should no let me emerge it without pulling in X11 (or XWayland if that is a valid alternative in this case).
Steps to Reproduce:
1. Install OBS: emerge -1 media-video/obs-studio
2. Try launching OBS: obs
Attempted path: share/obs/obs-studio/locale/en-US.ini
Attempted path: /usr/share/obs/obs-studio/locale/en-US.ini
Attempted path: share/obs/obs-studio/locale.ini
Attempted path: /usr/share/obs/obs-studio/locale.ini
Attempted path: share/obs/obs-studio/themes/Dark.qss
Attempted path: /usr/share/obs/obs-studio/themes/Dark.qss
info: CPU Name: AMD Ryzen 9 3900X 12-Core Processor
info: CPU Speed: 2198.627MHz
info: Physical Cores: 12, Logical Cores: 24
info: Physical Memory: 64249MB Total, 55914MB Free
info: Kernel Version: Linux 5.10.27-gentoo
info: Distribution: Gentoo Unknown
info: Session Type: wayland
info: Unable to open X display
info: Freeing OBS context data
No Segmentation fault
Created attachment 702375 [details]
emerge --info media-video/obs-studio media-video/ffmpeg dev-qt/qtgui
There's a pretty big re-factoring of the CMake configure parts coming up, so I'll probably handle this while adjusting things for that.
Thanks for the report!