>>11579
Thank you. I assume you are using my built release? The way PyInstaller packages/freezes the build means the environment and PATH of the process is a little odd under Linux. In order to call your system's external ffmpeg, I have to move some things around for the child process call.
Did this used to work for you? Maybe changed with the py3 release in 335?
If you hit
network->data->manage upnp, do you get a similar problem, or does it (after a few seconds) load your upnp mappings ok? (I am assuming here your router is happy with the mapping call, but even then I
think you'll get an error saying like "Router doesn't support upnp" rather than "Weird shit happened with the upnpc executable".
If that works, then it looks like your client can talk to exes with fixed paths, so the temporary solution here is likely to just download a Linux static build here:
https://johnvansickle.com/ffmpeg/
And literally put the 'ffmpeg' executable in your install_dir/bin folder.
Whether that works or not, I have written a new ''help->debug->report modes->subprocess report mode" mode to report more information about your path and subprocess arguments for tomorrow's release. Please attempt to do an ffmpeg import in v340 and see what environment info it gives. This may include private info, so please blank out personal stuff or just email it to me.
Furthermore, do you know where your system ffmpeg is? Is it in /usr/bin, /usr/local/bin, or somewhere else?