sfztools/sfizz-ui

Missing dependencies on .deb in ubuntu repository

TriYop opened this issue · 9 comments

TriYop commented

I recently installed sfizz from the ubuntu repository on an ubuntu studio (23.04) freshly installed.
When I try to launch sfizz UI from ardour/mixbus, I had the following error displayed in the terminal and the UI not showing.

suil error: Unable to open UI library /usr/lib/lv2/sfizz.lv2/Contents/Binary/sfizz_ui.so (/usr/lib/lv2/sfizz.lv2/Contents/Binary/sfizz_ui.so: undefined symbol: pango_font_metrics_get_height)

after a little googling, it seemed that this dependency was provided by libpango-perl which I installed and solved the issue.

May you please add the dependency to the package in order it is automatically installed by apt ?

Hi! Could you please provide a link to the package you downloaded and installed?

TriYop commented

Here is the package description page
https://packages.ubuntu.com/lunar/libpango-perl
and the package link in ubuntu repository
https://packages.ubuntu.com/lunar/amd64/libpango-perl/download

sorry, I mean the sfizz package, I need to understand if it's one of those we provide.

TriYop commented

that function is part of the pango library, which we include already (libpango1.0-dev, defined in pango/pango-font.h). I'll need some time to discuss with Paul about this.

paulfd commented

Hi! How did you install Ardour?

TriYop commented

Ardour is part of the base packages installed in ubuntu studio, so I use this package in ubuntu/lunar repository.
ardour/lunar,now 1:7.3.0+ds0-1 amd64 [installé, automatique]

The issue was the same with Mixbus (Harrison consoles) that has been installed through a tarball package in my /opt.

In carla, the UI was not showing up until I installed the [libpango-perl] package (which is not a requirement of libpango1.0-dev (I can't figure why as there seem to be no perl requirement with sfizz and pango dependencies seem to include what I expect)

Anyway.. I added that dependency only for the Ubuntu 23.04 package, let's see what happens, it would be nice to understand where is the culprit. Let us know if it is working now.

Closing, reopen if still an issue.