Hello ToneLib Community, I'd like to share an experience and suggest improvements for ToneLibGFX on Fedora with Wayland. TLGFX opens normally on Fedora when I extract the .deb file and run the extracted binary directly. However, secondary windows, such as the file import window, which is likely used to browse files on the system, don't work, possibly due to incompatibility with the Wayland graphical environment. Overall, ToneLibGFX works very well on Fedora—I can play, edit presets, and use the main features normally. However, I can't import external files into the program or export anything from it due to these window issues. Fedora is a wonderful system for music production, especially since it already has native PipeWire support, but ToneLibGFX doesn't yet have a fully compatible version. Below is a video from user @brunobmello25 who is experiencing the same issue using Fedora: My suggestion is that the team explore the following possibilities to improve the experience on Red Hat/Fedora systems: - Create a Flatpak version of ToneLibGFX for easier distribution and compatibility with different graphical environments. - Develop a native version for Red Hat systems like Fedora, aiming to resolve windowing and import/export issues. I am very grateful for the excellent work on ToneLibGFX and hope this suggestion helps with the growth and adoption of the software in the Linux ecosystem. Thank you!
Hi! Thanks for the suggestions—developing a native Fedora/Red Hat version or a Flatpak package would definitely improve usability. Meanwhile, some users run ToneLib GFX via Docker to handle missing dependencies, and Linux audio settings can affect the rhythm player. Your feedback is very helpful for improving compatibility!
Thanks for sharing your experience. It’s helpful to hear how ToneLibGFX behaves on Fedora with Wayland. It sounds like the main application runs fine, but the issue with secondary dialogs (like file import/export windows) might be related to Wayland compatibility or how the app handles window management outside of X11. It might be worth testing it through XWayland or launching it with a flag like --ozone-platform=x11 if supported. Hopefully the developers will consider improving native Wayland support in a future release since Fedora + PipeWire is becoming a popular setup for music production.
I think those are reasonable suggestions. A native Fedora/RHEL build would be nice, but even a well-maintained Flatpak could solve a lot of compatibility headaches since it provides a more consistent runtime across distributions. It also sounds like the issue may be related to the file dialog under Wayland rather than the audio engine itself, since the main application works fine. If the developers can reproduce it, that might make it easier to fix than a broader Linux compatibility problem. Hopefully a few more Fedora users can confirm the same behavior and provide logs, as that usually helps narrow these issues down much faster.