FS#51253 - [obs-studio] segfault on pressing start streaming

Attached to Project: Community Packages
Opened by Mio Iwakura (miotatsu) - Thursday, 06 October 2016, 03:51 GMT
Last edited by Jonathan Steel (jsteel) - Monday, 07 November 2016, 10:14 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When you hit the start streaming button in obs-studio it segfaults

Additional info:
* 0.16.2-1 x86_64
* tested on a custom built pc as well as a thinkpad w520


Steps to reproduce:
Set twitch stream key in the obs settings and then hit start streaming
This task depends upon

Closed by  Jonathan Steel (jsteel)
Monday, 07 November 2016, 10:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.16.4-1
Comment by Doug Newgard (Scimmia) - Thursday, 06 October 2016, 14:06 GMT
Is this only after the libx11 update?
Comment by Mio Iwakura (miotatsu) - Thursday, 06 October 2016, 18:35 GMT
Had not tried obs-studio pre libx11-1.6.4-1.
I just tested it again on my thinkpad after downgrading to libx11-1.6.3-1 and it still segfaulted as described.
Comment by Jonathan Steel (jsteel) - Friday, 07 October 2016, 10:22 GMT
Does recording work for you? And which DE/WM are you using?
Comment by Mio Iwakura (miotatsu) - Friday, 07 October 2016, 17:58 GMT
Just tried, it segfaults when attempting to record as well. I'm using i3.

I see "Couldn't initialize muxer" in the console output before it crashes when attempting to record. I also did a backtrace with gdb for you:
https://gist.github.com/miotatsu/cc7b601de24becdd7f60ff7f3a8c6775

Hope that info helps.
Comment by Jonathan Steel (jsteel) - Monday, 10 October 2016, 09:27 GMT Comment by Jonathan Steel (jsteel) - Wednesday, 19 October 2016, 09:53 GMT
I've found that running a tray "fixes" the issue. So run "trayer" for example and it doesn't crash. Not a solution but a workaround.
Comment by Mio Iwakura (miotatsu) - Wednesday, 19 October 2016, 17:33 GMT
I see that Jim has fixed it upstream as well. Will use your workaround until the next stable obs release; thanks :)

Loading...