FS#77235 - [obs-studio] crashes on startup when libva-vdpau-driver installed
Attached to Project:
Community Packages
Opened by A Web (aweb) - Sunday, 22 January 2023, 23:15 GMT
Last edited by Jonathan Steel (jsteel) - Friday, 26 May 2023, 17:18 GMT
Opened by A Web (aweb) - Sunday, 22 January 2023, 23:15 GMT
Last edited by Jonathan Steel (jsteel) - Friday, 26 May 2023, 17:18 GMT
|
Details
Description:
Additional info: * package version(s) obs-studio 29.0.0-1 libva-vdpau-driver 0.7.4-6 Note as of right now it also unfortunately happens with aur/obs-studio-git * config and/or log files etc. $ obs --verbose 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/themes/Yami.qss debug: Attempted path: /usr/share/obs/obs-studio/themes/Yami.qss info: Command Line Arguments: --verbose info: Using EGL/X11 info: CPU Name: AMD EPYC 7401P 24-Core Processor info: CPU Speed: 2610.836MHz info: Physical Cores: 24, Logical Cores: 48 info: Physical Memory: 128771MB Total, 124497MB Free info: Kernel Version: Linux 6.1.7-arch1-1 info: Distribution: "Arch Linux" Unknown info: Session Type: x11 info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.21.1 debug: found alternate keycode 62 for OBS_KEY_SHIFT which already has keycode 50 debug: found alternate keycode 105 for OBS_KEY_CONTROL which already has keycode 37 debug: found alternate keycode 108 for OBS_KEY_ALT which already has keycode 64 debug: found alternate keycode 129 for OBS_KEY_NUMPERIOD which already has keycode 91 debug: found alternate keycode 190 for OBS_KEY_REDO which already has keycode 137 debug: found alternate keycode 208 for OBS_KEY_VK_MEDIA_PLAY_PAUSE which already has keycode 172 debug: found alternate keycode 215 for OBS_KEY_VK_MEDIA_PLAY_PAUSE which already has keycode 172 debug: found alternate keycode 218 for OBS_KEY_PRINT which already has keycode 107 debug: found alternate keycode 231 for OBS_KEY_CANCEL which already has keycode 136 info: Qt Version: 6.4.2 (runtime), 6.4.2 (compiled) info: Portable mode: false debug: Attempted path: share/obs/obs-studio/themes/Dark/no_sources.svg debug: Attempted path: /usr/share/obs/obs-studio/themes/Dark/no_sources.svg qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_tbar_position_valueChanged(int) info: OBS 29.0.0-1 (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... debug: Created EGLDisplay 0x5608b341d260 info: Loading up OpenGL on adapter NVIDIA Corporation Quadro M5000/PCIe/SSE2 info: OpenGL loaded successfully, version 3.3.0 NVIDIA 525.85.05, shading language 3.30 NVIDIA via Cg compiler info: --------------------------------- info: video settings reset: base resolution: 1920x1080 output resolution: 1280x720 downscale filter: Bicubic fps: 30/1 format: NV12 YUV mode: Rec. 709/Partial info: NV12 texture support not available info: P010 texture support not available info: Audio monitoring device: name: Default id: default info: --------------------------------- debug: --------------------------------- debug: Loading module: decklink-captions.so warning: Failed to load 'en-US' text for module: 'decklink-captions.so' debug: --------------------------------- debug: Loading module: decklink-output-ui.so warning: Failed to load 'en-US' text for module: 'decklink-output-ui.so' debug: --------------------------------- debug: Loading module: decklink.so libDeckLinkAPI.so: cannot open shared object file: No such file or directory warning: A DeckLink iterator could not be created. The DeckLink drivers may not be installed warning: Failed to initialize module 'decklink.so' debug: --------------------------------- debug: Loading module: droidcam-obs.so debug: --------------------------------- debug: Loading module: frontend-tools.so debug: --------------------------------- debug: Loading module: image-source.so debug: --------------------------------- debug: Loading module: linux-alsa.so debug: --------------------------------- debug: Loading module: linux-capture.so debug: --------------------------------- debug: Loading module: linux-jack.so debug: --------------------------------- debug: Loading module: linux-pipewire.so info: [pipewire] No captures available debug: --------------------------------- debug: Loading module: linux-pulseaudio.so debug: --------------------------------- debug: Loading module: linux-v4l2.so debug: --------------------------------- debug: Loading module: obs-ffmpeg.so info: NVENC supported debug: VAAPI: Initializing display in vaapi_device_h264_supported debug: Libva: VA-API version 1.17.0 debug: Libva: Trying to open /usr/lib/dri/nvidia_drv_video.so debug: Libva: Found init function __vaDriverInit_1_13 Segmentation fault * link to upstream bug report, if any As of submission, no relevant bugs found here: https://github.com/obsproject/obs-studio/issues Steps to reproduce: On an arch linux machine with an nvidia graphics card, install obs-studio and libva-vdpau-driver. Start obs and it will crash as shown above. |
This task depends upon
Closed by Jonathan Steel (jsteel)
Friday, 26 May 2023, 17:18 GMT
Reason for closing: Upstream
Additional comments about closing: Not a packaging issue
Friday, 26 May 2023, 17:18 GMT
Reason for closing: Upstream
Additional comments about closing: Not a packaging issue
A trace might shed a bit more light. Please post a backtrace with symbols [1]
[1] https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod
https://github.com/obsproject/obs-studio/issues/8056
https://github.com/obsproject/obs-studio/issues/8104
Those traces don't contain debug symbols. Anyway, I just tried to repro in a VM and sure enough OBS crashes with a similar looking trace (attached). libva-vdpau-driver might be pretty old and crufty...but OBS crashing like that is not ideal. Assigning to relevant PM's for a look, but I doubt there's much that can be done.
If by upstream you mean OBS Studio (and not the driver), we just ask the user to uninstall the driver because the fix should be made on the driver.