When launching lmms, it fails to load ladspa-tap-plugins libraries which are marked as a dependency, these plugins are also used extensively by the presets contained by default and thus those presets are broken. Reproducible: Always Steps to Reproduce: 1. launch lmms Actual Results: Immediately tries to load libraries/plugins from ladspa-tap-plugins, but fails to do so with "undefined symbol" errors, causing them to be unusable. Expected Results: Immediately successfully load libraries/plugins from ladspa-tap-plugins
Created attachment 2091338 [details] Output when launching through the terminal
Hi there, I am also have trouble like you are, and I noticed that the files that have errors are a part of "ladspa-tap-plugins", not "lmms". Might want to file a bug under that package.
This is identical to bug 2373291
Ah, maybe not the same as darktable issue after all: those symbols are actually present in libmvec.so (but darktable's _ZGVbM4v_sqrtf is not). So maybe the build scripts are missing -lmvec somewhere?
The solution is imho not to add -lmvec to LDFLAGS (doesn't seem to work anyway), but to fix the ordering of objects and libraries on the linker cmd line. See https://src.fedoraproject.org/rpms/ladspa-tap-plugins/pull-request/1 for a possible fix.
*** Bug 2373291 has been marked as a duplicate of this bug. ***
Thomas, The fix you mentioned sounds good to me. ETA on when it could be available in the main repos? Thanks, -David
All, Thomas, Sorry for taking so long to fix this, especially since Thomas already provided a fix for this (which I missed). As is clearly demonstrated by the time it has taken me to even look a this at all, I don't really have time to properly maintain the ladspa-* packages in Fedora. If anyone who already is a Fedora packager wants to become a co-maintainer or even better fully take over maintainership of these packages let me know. About fixing this, while looking into fixing this I noticed that there is a new upstream 1.0.0 release which already correctly specifies the libraries last when linking and I can confirm that this fixes things. So I'm going to push out a long overdo update to the 1.0.0 version which also fixes this bug.
FEDORA-2026-63749d7404 (ladspa-tap-plugins-1.0.0-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-63749d7404
FEDORA-2026-63749d7404 (ladspa-tap-plugins-1.0.0-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-f35aa1ccde (ladspa-tap-plugins-1.0.0-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f35aa1ccde
FEDORA-2026-0955856643 (ladspa-tap-plugins-1.0.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-0955856643
FEDORA-2026-f35aa1ccde has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f35aa1ccde` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f35aa1ccde See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-0955856643 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-0955856643` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0955856643 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-f35aa1ccde (ladspa-tap-plugins-1.0.0-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-0955856643 (ladspa-tap-plugins-1.0.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.