Bug 17412

Summary:	ZynAddSubFx plugin does not work
Product:	Mageia	Reporter:	Lutz Lacher <l.lacher>
Component:	RPM Packages	Assignee:	Timothée Giet <animtim>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	lmms-1.1.2-1.mga5.src.rpm	CVE:
Status comment:

Description Lutz Lacher 2015-12-28 17:36:18 CET

Description of problem:

The GUI to configure the plugin does not open. If lmms is started from a shell it gives the following error message:

/usr/bin/../lib64/lmms//RemoteZynAddSubFx: error while loading shared libraries: libZynAddSubFxCore.so: cannot open shared object file: No such file or directory

But the file /usr/lib64/lmms/libZynAddSubFxCore.so exists and is part of the lmms-rpm, it looks like the plugin is looking for it in the wrong path. Starting lmms with LD_PRELOAD=/usr/lib64/lmms/libZynAddSubFxCore.so lmms works as expected 

Version-Release number of selected component (if applicable):
lmms-1.1.2-1.mga5.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open lmms
2. Add ZynAddSubFx plugin to song editor, click on it to configure 
3. Click the "Show Gui" button in the popup window


Reproducible: 

Steps to Reproduce:

David Walser 2015-12-28 23:12:50 CET

Assignee: bugsquad => animtim

Comment 1 Lutz Lacher 2016-01-03 11:05:31 CET

Same problem on Cauldron

Comment 2 Timothée Giet 2016-01-03 13:19:40 CET

Indeed, this is an upstream bug:
https://github.com/LMMS/lmms/issues/2269

The fix just landed in master, so next update should fix it for cauldron.

For mag5, I can try to backport this patch:
https://github.com/LMMS/lmms/pull/2118/files

Status: NEW => ASSIGNED

Comment 3 Timothée Giet 2016-01-03 18:51:49 CET

Hmm, after a closer look, the patch is not so straight-forward to backport to 1.1.2 or even to 1.1.3 as some concerned files seems to be renamed and changed a lot, so not something I can do for now.

Looks like best is too close the bug as it is an upstream one, which will be fixed in next release. 

What do you think about it? Which status should I use to close it?

Comment 4 Lutz Lacher 2016-01-04 15:46:56 CET

With next release you mean cauldron/MGA6, right? If so, it's ok for me since the workaround from the bug report works. Concerning the status: If it will be fixed in MGA6 you can close it as WONTFIX for MGA5. Anyway, thanks for looking after it.

Comment 5 Timothée Giet 2016-01-04 16:28:36 CET

Yes I meant for mga6. I hope there will be a new official release of lmms with the fix before mga6 freeze (if not, we can always package a git snapshot instead, but that is way less nice of course..).

Status: ASSIGNED => RESOLVED
Resolution: (none) => WONTFIX