Question / Help + Bug Report! OBS crashes on startup!

S

Smashlols

New Member
Hi I am trying to live stream to twitch but OBS keeps crashing when I run it.
I type OBS in to terminal and it runs but it never loads it just crashes!
I am running Ubuntu 14.04.
Code: 
b###n@b###in-Aspire-E1-571:~$ clear && 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/Default.qss
Attempted path: /usr/share/obs/obs-studio/themes/Default.qss
Attempted path: share/obs/obs-studio/license/gplv2.txt
Attempted path: /usr/share/obs/obs-studio/license/gplv2.txt
info: OBS 0.10.1 (linux)
info: Processor: 4 logical cores
info: Processor: Intel(R) Core(TM) i3-2348M CPU @ 2.30GHz
info: Physical Memory: 7802MB Total
info: Kernel Version: Linux 3.13.0-55-generic
info: Distribution: "Ubuntu" "14.04"
info: audio settings reset:
    samples per sec: 44100
    speakers:        2
    buffering (ms):  1000

info: X and Y: 902 489
Backbuffers: 2
Color Format: 3
ZStencil Format: 0
Adapter: 0

error: Failed to create OpenGL context.
error: Failed to create context!
*** Error in `obs': double free or corruption (out): 0x0000000001d47080 ***
Aborted (core dumped)
I also tried running:
Code: 
b###n@b###n-Aspire-E1-571:~$ sudo obs
[sudo] password for b###n:
Sorry, try again.
[sudo] password for b###n:
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/Default.qss
Attempted path: /usr/share/obs/obs-studio/themes/Default.qss
Attempted path: share/obs/obs-studio/license/gplv2.txt
Attempted path: /usr/share/obs/obs-studio/license/gplv2.txt
QObject::connect: invalid null parameter
info: OBS 0.10.1 (linux)
info: Processor: 4 logical cores
info: Processor: Intel(R) Core(TM) i3-2348M CPU @ 2.30GHz
info: Physical Memory: 7802MB Total
info: Kernel Version: Linux 3.13.0-55-generic
info: Distribution: "Ubuntu" "14.04"
info: audio settings reset:
    samples per sec: 44100
    speakers:        2
    buffering (ms):  1000

info: X and Y: 902 469
Backbuffers: 2
Color Format: 3
ZStencil Format: 0
Adapter: 0

error: Failed to create OpenGL context.
error: Failed to create context!
*** Error in `obs': double free or corruption (out): 0x000000000105da00 ***
If you need my computer specs it says them in the error thingy!
Log file:
Code: 
17:26:16: OBS 0.10.1 (linux)
17:26:16: Processor: 4 logical cores
17:26:16: Processor: Intel(R) Core(TM) i3-2348M CPU @ 2.30GHz
17:26:16: Physical Memory: 7802MB Total
17:26:16: Kernel Version: Linux 3.13.0-55-generic
17:26:16: Distribution: "Ubuntu" "14.04"
17:26:16: audio settings reset:
    samples per sec: 44100
    speakers:        2
    buffering (ms):  1000

17:26:16: X and Y: 902 489
Backbuffers: 2
Color Format: 3
ZStencil Format: 0
Adapter: 0

17:26:16: Failed to create OpenGL context.
17:26:16: Failed to create context!
Thanks for your help!
 
O

Osiris

Active Member
No need to bump a topic after a couple of minutes.
And you can't use OBS-mp, since your GPU does not have OpenGL 3.2+ support,
 
admalledd

admalledd

Member
Just a thought: is it possible to have obs return some basic driver/gpu info *before* opening the GL context or some such? Thus we might get GL+GPU info in the obs log file instead of depending on "glxinfo |grep OpenGL"? (even if it is a run said command line and return the info found?)

actually, this has bugged me enough to make a quick/ugly source patch. (should apply cleanly to 94edb7f5 , attached as glxinfo.patch.txt)

Borrowed most of the concept from glxinfo.c although I stripped most things (Eg obs tests for GLX 1.3+ already, no point in testing for gl/glx funcs that *will* exist already). Not really tested too much though... (and how to do this on windows?)
 

Attachments

  • glxinfo.patch.txt
    6.5 KB · Views: 86
admalledd

admalledd

Member
In all honesty, it might not be the best idea and should probably be re-written from the ground up. I still am learning how to play nice with OpenGL and all that. So might be better to look at the glxinfo source yourself or some such and re-implement it that way, I am rather sure I made a hash of it somehow. :D
 
You must log in or register to reply here.
Top