audacity-2.1.0 and ffmpeg wxWidgets 3.x


When trying to locate the ffmpeg library, I give (from ffmpeg-2.2.14) and audacity crashes (segmentation error).

Thanks for the report. Please provide the necessary information requested in the pink panel at the top of the page.

Where did FFmpeg come from? Did you compile Audacity against that FFmpeg?


Thank you for the answer. I am using slackware64-current. I compiled audacity from the source code. Before that I uninstalled ffmpeg-2.6.1 and installed ffmpeg-2.2.14.
After compiling audacity, I uninstalled ffmpeg-2.2.14, and re-installed ffmpeg-2.6.1, but I kept the libraries of version 2.2.14 somewhere. I had a segmentation violation when I did indicate the location of these libraries.

The best way to do this is to compile FFmpeg 2.2.x or 2.3.x, install it to /usr/local/lib, then build Audacity and it should link against your self-compiled FFmpeg.

If you used default ./configure when building Audacity it may already be linked against the FFmpeg in /usr/lib, but you have now changed that to an incompatible version (2.6.1). Hopefully Audacity wouldn’t crash, but you are not doing things correctly by the sound of it.

For the crash you currently get, feel free to post a stack trace by opening a terminal, browse to the location of the Audacity executable then launch Audacity in gdb:

$ gdb audacity

and then run Audacity:

(gdb) run


gdb gives the following:

Program received signal SIGSEGV, Segmentation fault.
0x00007fffecb2b3cd in g_type_check_instance_is_fundamentally_a ()
from /usr/lib64/…/lib64/

Finally I recompiled it with static ffmpeg-2.2.14 libraries, and reinstalled ffmpeg-2.6.1.

The problem disappears after recompiling with wxWidgets 2.8.12 instead of 3.0.2.

Thank you for the follow up.

Are you saying you still got a crash locating FFmpeg when you had compiled Audacity properly against FFmpeg 2.2.14, until you also compiled Audacity against wxWidgets 2.8.12?

Audacity does not support wx3.x. Please see Audacity is unstable if built with wxWidgets 3.x if you have not already done so.


Yes, this is what happened.

Thanks I created a bug report: