VST plugin scan fails

Hi, bit of a long shot but I’ll post this bugreport here 'cause it really got me stumped and not sure where to look anymore…

So, in the past I’ve succesfully used some Windows VST3 plugins (with yabridge) in Ardour - like TDR Kotelnikov, Ivgi2 etc…
Today I installed Ardour 7.2 and tried to re-scan my plugins, but now these VST scans fail. This is the message I see in plugin manager (e.g. Kotelnikov):

VST3 module-path '~/.vst3/yabridge/TDR Kotelnikov.vst3/Contents/x86_64-linux/TDR Kotelnikov.so'
[Info]: Scanning: ~/.vst3/yabridge/TDR Kotelnikov.vst3
19:29:17 [TDR Kotelnikov-9EIMRjqt] [Wine STDERR] /bin/sh: /opt/Ardour-7.2.0/lib/libreadline.so.8: no version information available (required by /bin/sh)
19:29:17 [TDR Kotelnikov-9EIMRjqt] [Wine STDERR] /bin/sh: /opt/Ardour-7.2.0/lib/libreadline.so.8: no version information available (required by /bin/sh)
19:29:17 [TDR Kotelnikov-9EIMRjqt] [Wine STDERR] /bin/sh: /opt/Ardour-7.2.0/lib/libreadline.so.8: no version information available (required by /bin/sh)
19:29:17 [TDR Kotelnikov-9EIMRjqt] [Wine STDERR] /bin/sh: /opt/Ardour-7.2.0/lib/libreadline.so.8: no version information available (required by /bin/sh)
19:29:17 [TDR Kotelnikov-9EIMRjqt] [Wine STDERR] /bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq, version READLINE_8.2
19:29:17 [TDR Kotelnikov-9EIMRjqt] Initializing yabridge version 5.0.3
19:29:17 [TDR Kotelnikov-9EIMRjqt] library:       '/lib64/libyabridge-vst3.so'
19:29:17 [TDR Kotelnikov-9EIMRjqt] host:          '/usr/bin/yabridge-host.exe'
19:29:17 [TDR Kotelnikov-9EIMRjqt] plugin:        '~/.wine/drive_c/Program Files/Common Files/VST3/TDR Kotelnikov.vst3'
19:29:17 [TDR Kotelnikov-9EIMRjqt] plugin type:   'VST3'
19:29:17 [TDR Kotelnikov-9EIMRjqt] realtime:      'yes'
19:29:17 [TDR Kotelnikov-9EIMRjqt] sockets:       '/run/user/1000/yabridge-TDR Kotelnikov-9EIMRjqt'
19:29:17 [TDR Kotelnikov-9EIMRjqt] wine prefix:   '~/.wine'
19:29:17 [TDR Kotelnikov-9EIMRjqt] wine version:  '7.21 (Staging)'
19:29:17 [TDR Kotelnikov-9EIMRjqt] 
19:29:17 [TDR Kotelnikov-9EIMRjqt] config from:   '<defaults>'
19:29:17 [TDR Kotelnikov-9EIMRjqt] hosting mode:  'individually, 64-bit'
19:29:17 [TDR Kotelnikov-9EIMRjqt] other options: '<none>'
19:29:17 [TDR Kotelnikov-9EIMRjqt] 
19:29:17 [TDR Kotelnikov-9EIMRjqt] Enabled features:
19:29:17 [TDR Kotelnikov-9EIMRjqt] - bitbridge support
19:29:17 [TDR Kotelnikov-9EIMRjqt] - CLAP support
19:29:17 [TDR Kotelnikov-9EIMRjqt] - VST3 support
19:29:17 [TDR Kotelnikov-9EIMRjqt] 
19:29:17 [TDR Kotelnikov-9EIMRjqt] The Wine host process has exited unexpectedly. Check the output above for more information.
terminate called without an active exception
Error: signal 6
 ---8<---
  /lib64/libc.so.6(+0x3d8e0) [0x7f11f76428e0]
  /lib64/libc.so.6(+0x907ec) [0x7f11f76957ec]
  gsignal
  abort
  /lib64/libstdc++.so.6(+0xa9ab5) [0x7f11f78a9ab5]
  /lib64/libstdc++.so.6(+0xb4fcc) [0x7f11f78b4fcc]
  /lib64/libstdc++.so.6(+0xb5037) [0x7f11f78b5037]
  /lib64/libyabridge-vst3.so(+0xaf7dc) [0x7f11f93447dc]
  /lib64/libstdc++.so.6(+0xe0983) [0x7f11f78e0983]
  /lib64/libc.so.6(+0x8e98d) [0x7f11f769398d]
  /lib64/libc.so.6(+0x115380) [0x7f11f771a380]
 --->8---
Scan Failed.

I’m using OpenSUSE Tumbleweed. I tried updating Bash (v5.2.15) and libreadline8 (v8.2.2.1) to latest version, yabridge=v5.0.3. Wine-staging is v7.21 … not sure I missed anything else ?
Or is this a yabridge error, since it generates some files and they somehow got corrupt ? It seemed to work ok before, so any insight is very welcome :slight_smile:

Bart.

I could be wrong but I think Wine-staging 7.21 broke yabridge…? Can you downgrade to 7.20 and try it? Or upgrade to 8.0rc which reportedly works now

1 Like

EDIT : in addition to my findings below; I temporarily replaced libreadline.so.8 with libreadline.so.6.3 and now the errors are gone and scan is OK :ok_hand:.

Thanks for the reply :slight_smile:

You were on to something at first; I was in fact using the wrong wine-staging package. I had 7.21 from OpenSUSE vendor and now switched to 7.20 from “multimedia” vendor (maintained by geekosdaw) - which yabridge is build against. I’ve re-build the .so files through yabridge now BUT … still the same error :frowning_face:

I also tried LinVst converter, but scanning those .so files in Ardour (or Mixbus for that matter) gives the same error messages.

/bin/sh: /opt/Ardour-7.2.0/lib/libreadline.so.8: no version information available (required by /bin/sh)
/bin/sh: symbol lookup error: /bin/sh: undefined symbol: rl_trim_arg_from_keyseq, version READLINE_8.2
...
The Wine host process has exited unexpectedly. Check the output above for more information.
terminate called without an active exception
Error: signal 6
 ---8<---
  /lib64/libc.so.6(+0x3d8e0) [0x7f38fae428e0]
  /lib64/libc.so.6(+0x907ec) [0x7f38fae957ec]
  gsignal
  abort
  /lib64/libstdc++.so.6(+0xa9ab5) [0x7f38fb0a9ab5]
  /lib64/libstdc++.so.6(+0xb4fcc) [0x7f38fb0b4fcc]
  /lib64/libstdc++.so.6(+0xb5037) [0x7f38fb0b5037]
  /lib64/libyabridge-vst2.so(+0x7b05c) [0x7f38fdbb505c]
  /lib64/libstdc++.so.6(+0xe0983) [0x7f38fb0e0983]
  /lib64/libc.so.6(+0x8e98d) [0x7f38fae9398d]
  /lib64/libc.so.6(+0x115380) [0x7f38faf1a380]
 --->8---
Scan Failed.

So maybe something changed in the readline.so.8 shipped with Ardour ? Maybe @paul or @x42 can shed some light here ? :pleading_face: :grin:

TIA
Bart

Ardour comes with a couple of libraries, and most are different than ones on your system.

There can be conflicts when mixing things (LinVST/wine from your OS) and Ardour. – Here specifically the system-wide shell (/bin/sh) and ardour’s libreadline (/opt/Ardour-7.2.0/lib/libreadline.so.8

The short term solution, pick one:

  • [re]move ardour’s readline. hopefully the system-wide readline.so is backwards compatible. sudo mv /opt/Ardour-7.2.0/lib/libreadline.* /tmp (if Ardour fails to start after that, move the files back)

  • use yabridge instead of LinVST, the former does not use a shell script to wrap plugins.

  • try a recent/upcoming ardour nightly (7.2.83 or later, Jan 6th) which comes with updated libreadline

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.