On Mon, 03 Oct 2022 03:07:30 +0100 Lyndon Brown <jnq...@gmail.com> wrote: > I have no idea at this time what the relevant difference is between > them that's causing this.
Update. So first of all I wondered whether differences in configure options could be relevant. Before, I'd just used --disable-skins2. So I rebuilt the upstream codebase with the following to duplicate much of the debian package config: ../configure --disable-skins2 --config-cache -- disable-update-check --enable-fast-install --enable-a52 --enable-aa -- enable-aribsub --enable-avahi --enable-bluray --enable-caca --enable- chromaprint --enable-chromecast --enable-dav1d --enable-dbus --enable- dca --enable-dvbpsi --enable-dvdnav --enable-faad --enable-flac -- enable-fluidsynth --enable-freetype --enable-fribidi --enable-gles2 -- enable-gnutls --enable-harfbuzz --enable-jack --enable-kate --enable- libass --enable-libmpeg2 --enable-libxml2 --enable-lirc --enable-mad -- enable-matroska --enable-mod --enable-mpc --enable-mpg123 --enable-mtp --enable-ncurses --enable-notify --enable-ogg --enable-opus --enable- pulse --enable-qt --enable-realrtsp --enable-samplerate --enable-sdl- image --enable-sftp --enable-shine --enable-shout --enable-skins2 -- enable-sndio --enable-soxr --enable-spatialaudio --enable-speex -- enable-srt --enable-svg --enable-svgdec --enable-taglib --enable-theora --enable-twolame --enable-upnp --enable-vdpau --enable-vnc --enable- vorbis --enable-x264 --enable-x265 --enable-zvbi --disable-aom -- disable-crystalhd --disable-d3d11va --disable-decklink --disable- directx --disable-dsm --disable-dxva2 --disable-fdkaac --disable- fluidlite --disable-freerdp --disable-goom --disable-gst-decode -- disable-libtar --disable-libva --disable-live555 --disable-macosx -- disable-macosx-avfoundation --disable-macosx-qtkit --disable-mfx -- disable-microdns --disable-opencv --disable-projectm --disable- schroedinger --disable-sparkle --disable-telx --disable-vpx --disable- vsxu --disable-wasapi This made no difference; it still worked fine unlike the debian package rebuild. So then I wondered about the possible affect of old artefacts within the build directory of the upstream code build. (It wasn't clean, since I'd previously used it for VLC dev work). Interestingly, deleting the build directory to create a fresh start DID make a difference. Using the same big configure command as above I now encounter the same issue as the debian package. This obviously might suggest that the "dirty" build directory contained a plugin binary from a previous build and this was causing some difference. I wondered about your use of --disable-libva and so with that removed from the above configure command, it was back to working again. So long story short, the problem would seem to be connected somehow to your use of --disable-libva.
