Bug Report Not Running. Not Compiling. Unable to use OBS on Debian Testing

Lymkwi

New Member
Hi,

I've been using OBS ever since I had something to record, circa 2014, almost always on Debian Linux. As of recently, OBS Studio was behaving fine, albeit for the occasional flashing of my X window captures.
Last night I decided to stream. After dealing with a few errors like "Output ID 'rtmp_output' not found", I realized I was running a version of OBS I had compiled myself almost a year and a half prior (when said flickering issues appeared and weren't being fixed).
So I removed it and tried the debian package.
Didn't work.

Code:
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/Acri.qss
Attempted path: /usr/share/obs/obs-studio/themes/Acri.qss
info: Command Line Arguments: --verbose
info: CPU Name: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
info: CPU Speed: 2793.787MHz
info: Physical Cores: 4, Logical Cores: 8
info: Physical Memory: 24081MB Total, 10504MB Free
info: Kernel Version: Linux 4.19.0-5-amd64
info: Distribution: "Debian GNU/Linux" Unknown
info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.20.4
info: Portable mode: false
Unknown property overflow
Unknown property overflow
[... roughly a hundred times that same message ...]
Unknown property overflow
Unknown property overflow
Unknown property overflow
QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_clicked()
QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_destroyed()
QMetaObject::connectSlotsByName: No matching signal for on_program_customContextMenuRequested(QPoint)
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
info: OBS 0.0.1 (linux)
info: ---------------------------------
info: ---------------------------------
info: audio settings reset:
        samples per sec: 44100
        speakers:        2
info: ---------------------------------
info: Initializing OpenGL...
info: Loading up OpenGL on adapter NVIDIA Corporation GeForce GTX 560M/PCIe/SSE2
info: OpenGL loaded successfully, version 3.2.0 NVIDIA 390.116, shading language 1.50 NVIDIA via Cg compiler
info: ---------------------------------
info: video settings reset:
        base resolution:   1920x1080
        output resolution: 1920x1080
        downscale filter:  Bilinear
        fps:               30/1
        format:            NV12
        YUV mode:          601/Partial
info: NV12 texture support not available
info: Audio monitoring device:
        name: Default
        id: default
info: ---------------------------------
warning: Failed to load 'en-US' text for module: 'decklink-ouput-ui.so'
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
Unknown property overflow
fish: “obs” terminated by signal SIGSEGV (Address boundary error)

My guess is that OBS Studio is trying to translate a string into a language for a local it doesn't understand, and things go haywire.

Here my output for "localectl".
Code:
   System Locale: LANG=en_US
                  LANGUAGE=en_US:en
       VC Keymap: n/a
      X11 Layout: fr
       X11 Model: pc105
     X11 Variant: oss
     X11 Options: terminate:ctrl_alt_bksp

After that I decided I was absolutely not gonna try and debug OBS on my own because this is not my responsibility, and I decided to go look on the official website for advice. I saw detailed instructions for compiling on Debian and Debian-based linux distros, and I followed them to a tee, until I ran into two compiling errors, documented in the log file attached.

For info on my setup, I'm running Debian Testing (so, I guess, bullseye), up to date (as of about thirty minutes ago) and rebooted (as of about twenty minutes ago). I'd gladly like to receive some assistance, as I am quite done with dealing with OBS misbehaving on my own, and I know no reasonable alternative to it.

EDIT: I tried to compile the current master of OBS Studio's repo.
 

Attachments

  • compile_log.txt
    43.1 KB · Views: 11

Tuna

Member
Just from reading the log - your custom compiled FFMPEG version needs to be compiled with the "-fPIC" flag so it can be properly linked to libobs.
 
Top