After upgrading to =media-video/obs-studio-29.0.0-r1, I cannot get OBS-Studio running. It generates a segmentation fault in libX11.so (see the attachments). > debug: Found portal inhibitor > debug: Attempted path: share/obs/obs-studio/locale/en-US.ini > debug: Attempted path: /usr/share/obs/obs-studio/locale/en-US.ini > debug: Attempted path: share/obs/obs-studio/locale.ini > debug: Attempted path: /usr/share/obs/obs-studio/locale.ini > debug: Attempted path: share/obs/obs-studio/locale/it-IT.ini > debug: Attempted path: /usr/share/obs/obs-studio/locale/it-IT.ini > info: Using preferred locale 'it-IT' > debug: Attempted path: share/obs/obs-studio/themes/Yami.qss > debug: Attempted path: /usr/share/obs/obs-studio/themes/Yami.qss > info: Using EGL/X11 > info: CPU Name: Intel(R) Core(TM) i7-4900MQ CPU @ 2.80GHz > info: CPU Speed: 3592.121MHz > info: Physical Cores: 4, Logical Cores: 8 > info: Physical Memory: 32077MB Total, 14401MB Free > info: Kernel Version: Linux 6.1.1-gentoo > info: Distribution: Gentoo "2.9" > info: Session Type: x11 > info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.21.1 > info: Qt Version: 5.15.8 (runtime), 5.15.8 (compiled) > info: Portable mode: false > QMetaObject::connectSlotsByName: No matching signal for on_tbar_position_valueChanged(int) > info: OBS 29.0.0 (linux) > info: --------------------------------- > info: --------------------------------- > info: audio settings reset: > samples per sec: 48000 > speakers: 2 > max buffering: 960 milliseconds > buffering type: dynamically increasing > info: --------------------------------- > info: Initializing OpenGL... > info: Loading up OpenGL on adapter NVIDIA Corporation NVIDIA GeForce GTX 780M/PCIe/SSE2 > info: OpenGL loaded successfully, version 3.3.0 NVIDIA 470.161.03, shading language 3.30 NVIDIA via Cg compiler > info: --------------------------------- > info: video settings reset: > base resolution: 1920x1080 > output resolution: 1920x1080 > downscale filter: Lanczos > fps: 60/1 > format: NV12 > YUV mode: Rec. 709/Full > info: NV12 texture support not available > info: P010 texture support not available > info: Audio monitoring device: > name: Predefinito > id: default > info: --------------------------------- > warning: Failed to load 'en-US' text for module: 'decklink-captions.so' > warning: Failed to load 'en-US' text for module: 'decklink-output-ui.so' > libDeckLinkAPI.so: impossibile aprire il file oggetto condiviso: File o directory non esistente > warning: A DeckLink iterator could not be created. The DeckLink drivers may not be installed > warning: Failed to initialize module 'decklink.so' > info: [pipewire] Available captures: > info: [pipewire] - Desktop capture > info: [pipewire] - Window capture > info: [obs-browser]: Version 2.19.0 > info: [obs-browser]: CEF Version 103.0.5060.134 (runtime), 103.0.0-5060-shared-textures_143.2591+g4204d54+chromium-103.0.5060.134 (compiled) > info: NVENC supported > Errore di segmentazione (core dump creato) Reproducible: Always Steps to Reproduce: 1. Emerge =media-video/obs-studio-29.0.0-r1 2. Launch OBS-Studio 3. No GUI shown... Actual Results: OBS-Studio starts but immediately crashes Expected Results: Getting the OBS-Studio GUI
Here the dmesg error: > [11251.490259] obs[893140]: segfault at d8 ip 00007efd0b2ed130 sp 00007fff88f5a208 error 4 in libX11.so.6.4.0[7efd0b2db000+8a000] likely on CPU 7 (core 3, socket 0) > [11251.490271] Code: 2e 0f 1f 84 00 00 00 00 00 90 8b 47 1c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 8b 47 74 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 87 d8 00 00 00 c3 0f 1f 84 00 00 00 00 00 48 63 f6 48 c1 e6
Created attachment 849580 [details] ebuild --info
Did it work with a previous version, with the same settings/build configuration, and if possible to try, does that version still work? I notice the pipewire related messages, which I've not had a chance to test really aside from building with support for it enabled, but I believe I was missing something for the video capture parts when doing that, so that makes me wonder... A backtrace via 'gdb' might be interesting, as well as trying with a clean "user profile" (that is, with no previous scenes and such already defined).
If the backtrace mentions 'vaapi', I might guess it could be related to upstream issue [1], although I don't think we have such a package laying around (in ::gentoo). 1. https://github.com/obsproject/obs-studio/issues/8056
(In reply to Chiitoo from comment #3) > Did it work with a previous version, with the same settings/build > configuration, and if possible to try, does that version still work? > > I notice the pipewire related messages, which I've not had a chance to test > really aside from building with support for it enabled, but I believe I was > missing something for the video capture parts when doing that, so that makes > me wonder... > > A backtrace via 'gdb' might be interesting, as well as trying with a clean > "user profile" (that is, with no previous scenes and such already defined). Yes it works! If I downgrade back to 28.x version OBS-Studo works again. I will try wiping the profile. Iade
(In reply to Chiitoo from comment #3) > Did it work with a previous version, with the same settings/build > configuration, and if possible to try, does that version still work? > > I notice the pipewire related messages, which I've not had a chance to test > really aside from building with support for it enabled, but I believe I was > missing something for the video capture parts when doing that, so that makes > me wonder... > > A backtrace via 'gdb' might be interesting, as well as trying with a clean > "user profile" (that is, with no previous scenes and such already defined). UPDATE: Wiping profile didn't help... Iade
(In reply to Chiitoo from comment #4) > If the backtrace mentions 'vaapi', I might guess it could be related to > upstream issue [1], although I don't think we have such a package laying > around (in ::gentoo). > > 1. https://github.com/obsproject/obs-studio/issues/8056 Bingo! This was the root issue :) THX Iade
(In reply to Iade Gesso from comment #7) > (In reply to Chiitoo from comment #4) > > If the backtrace mentions 'vaapi', I might guess it could be related to > > upstream issue [1], although I don't think we have such a package laying > > around (in ::gentoo). > > > > 1. https://github.com/obsproject/obs-studio/issues/8056 > > Bingo! This was the root issue :) THX > > > Iade Thanks! Did you have a package for it installed from an overlay or something?
(In reply to Chiitoo from comment #8) > (In reply to Iade Gesso from comment #7) > > (In reply to Chiitoo from comment #4) > > > If the backtrace mentions 'vaapi', I might guess it could be related to > > > upstream issue [1], although I don't think we have such a package laying > > > around (in ::gentoo). > > > > > > 1. https://github.com/obsproject/obs-studio/issues/8056 > > > > Bingo! This was the root issue :) THX > > > > > > Iade > > Thanks! > > Did you have a package for it installed from an overlay or something? Yes it was in my local overlay and I forgot to have it installed. Iade
Alrighty, will close this up since I don't think there is anything for us to do here. Closing as cantfix as it's something that should be fixed upstream, which at this time will not do that for this particular configuration. Thank you for the report!
