Yes, when the package manager version didn't work. I downloaded 1.2.22 from here. Then, when that didn't work I jumped back to a version (1.1.16 IIRC) that worked, then I split the difference until I landed on 1.2.20 as the one (tarball) that worked on my ssystem and 1.2.21 as the version where the built tarballs stopped working on my system.
Thats what I had done originally. The package manager updated my plugins to 1.2.22 and the vst versions stopped working. This began my investigation into what happened and determining that 1.2.20 worked, but not 1.2.21.
yes
yup, adding "ui" to features resolved not having a ui. who'd a thunk it.
I'm using Manjaro (based on Arch).
FWIW, I built 1.2.20 from source, and ldd returns: linux-vdso.so.1 (0x00007ff598eb7000) /usr/NX/lib/libnxegl.so (0x00007ff598200000) libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x00007ff598ddc000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007ff597e00000) libm.so.6 => /usr/lib/libm.so.6 (0x00007ff598508000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007ff598daf000) libc.so.6 => /usr/lib/libc.so.6 (0x00007ff597c10000) /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff598eb9000) libdl.so.2 => /usr/lib/libdl.so.2...
readelf of the 1.22 binary returns: ELF Header: Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: DYN (Shared object file) Machine: Advanced Micro Devices X86-64 Version: 0x1 Entry point address: 0x0 Start of program headers: 64 (bytes into file) Start of section headers: 12836440 (bytes into file) Flags: 0x0 Size of this header: 64 (bytes) Size of program headers: 56 (bytes) Number...
ditto: [lsp-plugins.vst.1.20]$ chmod a+x liblsp-plugins-vst2.so [lsp-plugins.vst.1.20]$ ldd liblsp-plugins-vst2.so ldd: warning: you do not have execution permission for `./liblsp-plugins-vst2.so' not a dynamic executable