-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation Fault on Ubuntu 13.10 #50
Comments
Seems to be a bug in the version of libav that Ubuntu is using. Any attempt to use x264 fails, not just in SSR, but also in the official command-line tool (avconv). I can't fix that. The bug report is here: There's no way to work around this, unless you compile x264 from source. You can still use VP8 (it is slower though). |
I've marked the Ubuntu bug as affecting me, and will encourage anyone else I find to do the same. I've tried working around the bug by compiling libx264 from source, but the versioning of libx264.so is... odd... compared to what I'm used to seeing. Compiling the current git produces libx264.so.138, but it appears that something in ssr or libavcodec is specifically looking for version 123. Symlinking the new dll produces a different crash when it's used: "simplescreenrecorder: symbol lookup error: /usr/lib/x86_64-linux-gnu/libavcodec.so.53: undefined symbol: x264_encoder_open_123" I used 'apt-get source' to get the source code for v123, but it of course had the same bug when I compiled it and tried to use it. I looked at the snapshots at ftp://ftp.videolan.org/pub/x264/snapshots/, but the ones from February (when you indicated it was fixed) are version 129 and later - so I assume they would not work either due to the mangling referring specifically to 123.. I attempted to hackishly override the API version in x264.h, but I guess there have been significant API changes between 138 and 123, because the resulting .so file also segfaults. I'm guessing I have to do more than build x264? Maybe build libavcodec from source over the current version of x264? It'll probably make more sense to me after I get some sleep. |
NEVERmind... duh... it came to my sleep addled mind as soon as I posted: All I needed to do is compile the Ubuntu source (123) version with --extra-cflags=-fno-aggressive-loop-optimizations. I did that, and it works fine! So, as a workaround, Ubuntu users can do something along the lines of:
|
Hi 3vi1, Great work around!!! Thanks!!! Now I have to get my video driver working again!!! Be Blessed!!!
|
I've uploaded a patched x264 package to my PPA (with the backported upstream patch instead of the workaround). This appears to fix it. |
Maarten, Thanks for following up! I right now the work around is doing great!!! I Be Blessed!!! Elbennit On Sun, Oct 20, 2013 at 12:49 PM, MaartenBaert notifications@github.comwrote:
|
I am using the
0.1.1-1~ppa1~saucy1
version from the PPA. I am also on amd64 with the Nvidia 304.88 proprietary driver.The text was updated successfully, but these errors were encountered: