Bug 2368336

Summary: Cannot load library/undefined symbol errors with ladspa-tap-plugins dependency
Product: [Fedora] Fedora Reporter: fedusr10
Component: ladspa-tap-pluginsAssignee: Hans de Goede <hans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 42CC: avrunin, chipmand, germano.massullo, hdegoede, jwf, pampelmuse, thomas.moschny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ladspa-tap-plugins-1.0.0-1.fc44 ladspa-tap-plugins-1.0.0-1.fc43 ladspa-tap-plugins-1.0.0-1.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-01-31 18:17:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output when launching through the terminal none

Description fedusr10 2025-05-23 23:28:58 UTC
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

Comment 1 fedusr10 2025-05-23 23:32:11 UTC
Created attachment 2091338 [details]
Output when launching through the terminal

Comment 2 David C. Chipman 2025-06-17 22:39:42 UTC
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.

Comment 3 Miloš Komarčević 2025-06-18 09:10:40 UTC
This is identical to bug 2373291

Comment 4 Miloš Komarčević 2025-06-20 11:49:00 UTC
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?

Comment 5 Thomas Moschny 2025-06-29 17:03:09 UTC
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.

Comment 6 Thomas Moschny 2025-06-29 17:04:12 UTC
*** Bug 2373291 has been marked as a duplicate of this bug. ***

Comment 7 David C. Chipman 2025-06-30 00:35:54 UTC
Thomas, 

The fix you mentioned sounds good to me. ETA on when it could be available in the main repos? Thanks, 

-David

Comment 8 Hans de Goede 2026-01-31 17:28:12 UTC
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.

Comment 9 Fedora Update System 2026-01-31 17:37:02 UTC
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

Comment 10 Fedora Update System 2026-01-31 18:17:16 UTC
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.

Comment 11 Fedora Update System 2026-01-31 22:38:26 UTC
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

Comment 12 Fedora Update System 2026-01-31 22:38:26 UTC
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

Comment 13 Fedora Update System 2026-02-01 01:24:48 UTC
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.

Comment 14 Fedora Update System 2026-02-01 02:30:11 UTC
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.

Comment 15 Fedora Update System 2026-02-09 01:04:45 UTC
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.

Comment 16 Fedora Update System 2026-02-09 01:13:55 UTC
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.