Bug#963013: marked as done (invada-studio-plugins-lv2 edit dialog suil error)
Your message dated Sun, 23 Nov 2025 17:59:28 +0000
with message-id <[🔎] E1vNEMy-002DJw-22@fasolo.debian.org>
and subject line Bug#1120754: Removed package(s) from unstable
has caused the Debian Bug report #963013,
regarding invada-studio-plugins-lv2 edit dialog suil error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
963013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963013
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: invada-studio-plugins-lv2 edit dialog suil error
- From: "Paulo S. Pinheiro" <pinus.sc@gmail.com>
- Date: Wed, 17 Jun 2020 15:09:39 -0300
- Message-id: <84b6baad-3185-8998-6e30-9d3b7293785f@gmail.com>
Package: invada-studio-plugins-lv2
Version: 1.2.0+repack0-8
Uname: Linux 5.4.0-37-lowlatency x86_64
DistroRelease: Ubuntu 20.04
Description:
I've tried before to report thist bug in Lanunchpad to Ubuntu Developers, but they directed me to Debian, because they import the package unchanged.
Here's what happens:
Since I upgraded to Ubuntustudio 20.04 (Intel 64-bit) I can't open the INVADA plugins edit dialog on Ardour5 (rev 1:5.12.0-3ubuntu4). No error message dialog.
Running Ardour5 on terminal and trying again I get the following message line (example: Invada Early Reflection Reverb):
"suil error: Unable to open UI library /usr/lib/lv2/invada.lv2/inv_erreverb_gui.so (/usr/lib/lv2/invada.lv2/inv_erreverb_gui.so: undefined symbol:__sinh_finite)"*.
The inv_erreverb_gui.so* is correctly in */usr/lib/liv2/invada.lv2 directory.
The Ardour native generic control editor dialog works fine for the plugins.
I noticed some LV2 plugins editors open correctly, some others don't. Here are the ones with the problem:
. Invada Compressor
. Invada Early Reflection Reverb
. Invada High Pass Filter
. Invada Input Module
. Invada Low Pass Filter
. Invada Meter
. Invada Stereo Phaser
. Invada Tube Distortion
The "good" ones:
. Invada Delay Munge
. Invada Test Tones
The error messages for the other problematic plugins are similar to the one above. The files are all there on the expected directory. Haven't find any workaround by Ubuntu Studio or Ardour.
When I tried to compile the Ubuntu package (invada-studio-plugins-lv2_1.2.0+repack0) from source I got the error:
"dpkg-checkbuilddeps: erro: Unmet build dependencies: debhelper (>= 11) libgtk2.0-dev lv2-dev"
In my system I have:
debhelper: 12.10ubuntu1
libgtk2.0-dev: 2.24.32-4ubuntu4
lv2-dev: 1.16.0-1
So, it seems to me that the plugin is not compatible with the new libgtk2.0-dev library, and/or lv2-dev.
But I'm very newbie.
Any other information you need to solve the problem, please let me know.
Thank you in Advance
Paulo S. Pinheiro
--- End Message ---
--- Begin Message ---
Version: 1.2.0+repack0-10+rm
Dear submitter,
as the package invada-studio-plugins-lv2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1120754
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
Reply to: