Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#64658 - [ardour] Ardour cannot find its built-in plugins
Attached to Project:
Community Packages
Opened by James Crompton (DonJaime) - Tuesday, 26 November 2019, 18:03 GMT
Last edited by David Runge (dvzrv) - Thursday, 28 November 2019, 08:31 GMT
Opened by James Crompton (DonJaime) - Tuesday, 26 November 2019, 18:03 GMT
Last edited by David Runge (dvzrv) - Thursday, 28 November 2019, 08:31 GMT
|
DetailsArdour comes with a small set of built-in LV2 plugins (in /usr/lib/ardour5/LV2/).
Version 5.12-12 can't find them. When opening a session that uses these plugins, ardour notes that it can't find them, and replaces them with a non-functional stub. Version 5.12-11 did not have this problem. |
This task depends upon
Closed by David Runge (dvzrv)
Thursday, 28 November 2019, 08:31 GMT
Reason for closing: Fixed
Additional comments about closing: Regression fixed (and upstreamed) in 5.12-13
Thursday, 28 November 2019, 08:31 GMT
Reason for closing: Fixed
Additional comments about closing: Regression fixed (and upstreamed) in 5.12-13
I think it's likely due to the waf fix I did (python2 -> python3).
It seems the manifest.ttl now points `lv2:binary` to a file, that doesn't have a `.so` suffix.
I'll try to fix this in the build system asap.