Hello, I recently do full system update. The issue that came up is that all of my screen recording program doesn’t work anymore.
OBS Studio
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/themes/Yami.qss
debug: Attempted path: /usr/share/obs/obs-studio/themes/Yami.qss
info: Using EGL/X11
info: CPU Name: AMD Ryzen 5 3500 6-Core Processor
info: CPU Speed: 4068.685MHz
info: Physical Cores: 6, Logical Cores: 6
info: Physical Memory: 15917MB Total, 7597MB Free
info: Kernel Version: Linux 6.1.26-1-MANJARO
info: Distribution: "Manjaro Linux" Unknown
info: Session Type: x11
info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.21.1
info: Qt Version: 6.5.0 (runtime), 6.4.2 (compiled)
info: Portable mode: false
qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_tbar_position_valueChanged(int)
info: OBS 29.0.2-2 (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 1650/PCIe/SSE2
info: OpenGL loaded successfully, version 3.3.0 NVIDIA 530.41.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/Partial
info: NV12 texture support not available
info: P010 texture support not available
info: Audio monitoring device:
name: Default
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: 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'
info: [pipewire] No captures available
warning: v4l2loopback not installed, virtual camera disabled
info: NVENC supported
zsh: segmentation fault (core dumped) obs
simplescreenrecorder (AUR)
simplescreenrecorder: error while loading shared libraries: libavformat.so.59: cannot open shared object file: No such file or directory
gpu-screen-recorder-git (AUR)
window name: [Stable Update] 2023-05-07 - Kernels, KDE Gear 23.04.0, KDE Frameworks 5.105.0, Qt5, Firefox, Thunderbird - Announcements / Stable Updates - Manjaro Linux Forum — Mozilla Firefox, window id: 115343422
window name: SG Physics 2D (DEBUG), window id: 119537668
gpu-screen-recorder: error while loading shared libraries: libavcodec.so.59: cannot open shared object file: No such file or directory
waitpid failed: No child processes
Notification: title: GPU Screen Recorder, body: Failed to save video. Either your graphics card doesn't support GPU Screen Recorder or you don't have enough disk space to record a video
Hmm, looks like this wasn’t the issue but yes, it is obs problem. It just a coincidence that the error happened together with every other screen recording program I had installed.
I guess you dont need VDPAU backend for VAAPI then ?
(useful if vdpau is superior or the only acceleration available while an application only provides VAAPI)
QVariant: Provided metatype for 'QColor' does not support destruction and copy construction
info: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Mic/Aux)
zsh: segmentation fault (core dumped) obs
It’s still record fine, I’ll just keep it like this for now.
(I have a ryzen 2500u and use both VAAPI and VDPAU and have the faux backend ones … I ended up using vaapi predominantly … but amdgpu can handle both)
In your case … you probably want to focus on having vdpau well and good … as well as use its backend for vaapi … because you use nvidia. and vdpau is for nvidia and vaapi is not … so in cases, such as your browser, that only VAAPI is available … you want to use the vdpau backend for it.
(things that arent good at having a sane default or fallback can have problems if hw-accel is not properly configured both on the system and the application in question … a good example is VLC … which has a miriad of issues if you dont handle hw-accel properly)