Bug 1648547 - The LV2 zynadd plugin is not shown among possible plugins
Summary: The LV2 zynadd plugin is not shown among possible plugins
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lv2-zynadd-plugins
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-10 13:53 UTC by Franco Bugnano
Modified: 2019-11-27 19:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:51:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Franco Bugnano 2018-11-10 13:53:57 UTC
Description of problem:
When tracking MIDI on Muse, with the lv2-zynadd-plugins installed, there is no zynadd (or similar) LV2 plugin to chose from

Version-Release number of selected component (if applicable):
lv2-zynadd-plugins-1-19.fc29.x86_64


How reproducible:
always

Steps to Reproduce:
1. Install lv2-zynadd-plugins and muse
2. Open muse
3. Right click to add an LV2 instrument

Actual results:
No zynadd (or similar) is shown among tha available plugins

Expected results:
zynadd is shown and can be used as an LV2 instrument

Additional info:
When running muse from the command line, this error is shown:
	 LV2: zynadd: Required feature: http://home.gna.org/lv2dynparam/rtmempool/v1: not supported!

It is not a bug on muse either, as I tried to use this plugin also in ardour, and here the behaviour is different, but still broken, in the sense that the zynadd LV2 plugin is shown, but if I attempt to use it, it is not added. And when tunning ardour from the command line this error is shown:
http://home.gna.org/lv2dynparam/rtmempool/v1 extension is required

Comment 1 Ben Cotton 2019-10-31 20:32:05 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-11-27 19:51:15 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.