Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatible GLIBC on Fedora 36 #194

Closed
1 task done
carterisonline opened this issue Aug 9, 2022 · 8 comments
Closed
1 task done

Incompatible GLIBC on Fedora 36 #194

carterisonline opened this issue Aug 9, 2022 · 8 comments
Labels
invalid This doesn't seem right

Comments

@carterisonline
Copy link

Thanks for giving yabridge a shot!

  • I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

Issue occurs in Bitwig (Flatpak) after installing yabridge-testing and wine-tkg-testing from COPR. yabridge-testing on COPR is only provided for Fedora 36, but glibc-2.34 is only available for Fedora 35 (36 uses ver. 2.35)

Bitwig Log Snippet:
Failed to load VST 3 plug-in /var/home/carter/.vst3/yabridge/Arturia/Rev INTENSITY.vst3: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /var/home/carter/.vst3/yabridge/Arturia/Rev INTENSITY.vst3/Contents/x86_64-linux/Rev INTENSITY.so)

Operating system

Fedora 36

How did you install yabridge?

yabridge-testing COPR

yabridge version

4.0.3

yabridgectl version

4.0.3

Wine version

wine-tkg 7.14

Plugin

Any

Plugin type

VST3

Plugin architecture

64-bit

Host

Bitwig Studio 4.3.4 (Flatpak)

Desktop environment or WM

GNOME 42.3 on Wayland

GPU model

NVIDIA GTX 1080

GPU drivers and kernel

Linux 5.18.16-200.fc36.x86_64

Debug log

No response

Anything else?

No response

@plaimbock
Copy link
Contributor

Hey Carter, creator of the wine/yabridge coprs here. I don't use the Bitwig Flatpak (I convert the deb to an rpm and install that) so no idea. Maybe the Bitwig flatpak was created on Fedora 35? Just a wild guess. You can rebuild the flatpak on Fedora 36. The manifest is here: https://github.com/flathub/com.bitwig.BitwigStudio Maybe @abique has an idea?

@plaimbock
Copy link
Contributor

Also check: bitwig/bitwig-studio-flatpak#24

@carterisonline
Copy link
Author

I tried converting the latest deb to rpm, trying with this script, with Alien and with FPM, where the issue still occurred on all three. Still encountered the same issue even with rebuilding the flatpak from manifest. As far as I've looked, there's no safe method of installing glibc-2.34 on F36.

@robbert-vdh
Copy link
Owner

The Flatpak version of Bitwig uses a runtime that's based on Ubuntu 21.10, which uses an older version of glibc than the one Fedora 36 ships with. But even if you'd use a yabridge version compiled against an older glibc, you'd still run into the other problems from #135. You'll need to use a non-Flatpak version of Bitwig to be able to use yabridge and other plugins that won't run under the Flatpak runtime. On Arch you can just install bitwig-studio from the AUR, but I don't know what the easiest way to install regular non-Flatpak Bitwig on Fedora is.

@plaimbock
Copy link
Contributor

FWIW I use this spec file to convert the deb to an rpm and I don't recall any issues with Arturia Pygments or the V Collection 8 (on Fedora 36).
bitwig-studio.spec.txt
.

@carterisonline
Copy link
Author

carterisonline commented Aug 20, 2022

QUICK FIX FOR THOSE WHO ARE LOOKING:

I was unable to get it to work on Fedora itself, even with the .spec file graciously provided by @plaimbock, but I DID find a way to make it work. I still think this issue should stay open since this is a temporary fix. In this example, I'll be using Bitwig + Yabridge on an Arch Linux container.

  1. Install Distrobox
  2. Create an Arch container like so: distrobox-create --name bitwig --image archlinux:latest
  3. Enter your container: distrobox enter bitwig
  4. Install an AUR helper (I use Paru)
  5. Install Bitwig Studio: e.g paru -S bitwig-studio
  6. Install gtk3, libxkbcommon and xcb-util
  7. Enable the multilib repository by adding these lines to /etc/pacman.conf:
[multilib]
Include = /etc/pacman.d/mirrorlist
  1. Perform a hard repository sync: sudo pacman -Syy
  2. Install wine, yabridge and yabridgectl
  3. Delete the ~/.vst3 and other folders previously generated by yabridgectl. They will cause issues because Distrobox mounts your /home/$USER/ folder inside the container by default.
  4. Resync plugins using yabridgectl sync

@rayacode
Copy link

rayacode commented Aug 24, 2022

same issue on Opensuse tumbleweed with bitwig flatpack, trying to get to work with scaler 2
below error is same for all the .so and .vst3 files

/home/.../.vst/yabridge/Scaler2.so

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 2 plug-in /home/.../.vst/yabridge/Scaler2.so: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/.../.vst/yabridge/Scaler2.so)

@robbert-vdh
Copy link
Owner

Closing this since this is not a yabridge issue.

@robbert-vdh robbert-vdh added the invalid This doesn't seem right label Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

4 participants