Since last weekend update to my OS based on Arch, vital interface is now showing black, although I can still interact and the audio still works properly.
During my attempts, I tried standalone and through reaper and bitwig. Vital tends to crash on opening, but when it works, it’s a black interface. VST3, CLAP, and standalone version, same issue across the board.
Only output I am getting from standalone via the terminal is this:
fish: Job 1, ‘Vital’ terminated by signal SIGKILL (Forced quit)
My ram usage barely goes up, and I had over 20Gb free at the time of testing.
After few attempts, the synth may open but with the black interface, and the ability to produce sound.
The system is running in wayland, and bitwig/vital run trhough Xwayland, which was not an issue before.
I suspect the fact that I am on AMD and a new major version of mesa was pushed (26.0.1).
Any help to try to figure it out would be greatly appreciated. Cheers
Ok so, I suspect the issue to happen more as 26.x is rolled out on more distributions, leaving this for the future:
I got time to downgrade the graphic drivers to mesa 25.3.5 and vital now has an interface again, as expected. Every mesa libs (that are not provided directly by the driver) are still running on the 26.0.1 base.
It is either an issue on the side of the core driver, or in how vital interface handles rendering. I don’t expect this to be looked into as this project seems abandoned.
I’ll update this post when a new mesa update is pushed for informative purposes. But for now, vital being the only affected plugins/software, I will use something else.
what I mean is that on other threads people mentioned not getting a reply from support in 2 months etc, I don’t think the synth has been updated in couple years either.
I may try and see if I can report the issue somewhere around mesa development, in case it is related to a bug there, otherwise, I think we are out of luck and Vital will fade out from being usable on linux once every distro runs mesa 26+.
For a bit of an update, mesa 26.0.3 now and the issue remains.
I’m on Manjaro Stable, which just today updated to Mesa 26 (26.0.2). Running GNOME on Wayland w/ AMD graphics, I have this issue, but I’m not seeing it on my laptop running Cinnamon/Xorg/Intel graphics. I really hope this is fixable, I’d be gutted to no longer be able to use Vital consistently on my Linux machines.
Interesting, I am not familiar with intel graphics, and fairly new to linux, but from my understanding, intel graphics use mesa libs with a specific driver?
In my case with the working downgrade mesa libs were still 26.* only the proper mesa package is not playing nice once on 26.*
I opened a bug ticket on mesa’s today.
Hopefully it can be fixed, and hopefully before mesa 26 hits a wider range of distros.
Tried Vitalium, the fork from Distrho and it works, it’s old and lacking features from 1.5 though. (also needs to get waveforms and presets from vital as it comes without any)
1.6.3 crashes Renoise on Ubuntu 26.04, both on Wayland and X11 with a NVIDIA GeForce RTX 5070. When inserting the .VST3, the GUI is blank on Wayland and Renoise crashes immediately. On X11, when inserting the .VST3, the GUI is shown, but Renoise crashes when inserting another instance of Vital. This happens also when sandboxing the plugin.
The same happens in REAPER. This is an old bug and has obviously not been fixed. Vital stays ununsable on Linux for me.
the crash is not affected by os version. people have it on windows 11 as well as windows 7. the gfx card is also not affecting the crash; some have new extremely fast gfx cards and still experience the crash whereas on older pc with old gfx card vital works fine. im on win 7 with gtx 980 and vital is crashing everytime. doesnt matter if it’s standalone or vst either. i tried disabling the driver and vital crashes but it’s not even showing anything. when driver is enabled the crash shows a black turning to white background then crashes after 2 secs. mr tytel switched from opengl to directx 11 from version 1.5.1 and onwards but someone who has directx 12 still gets the same crash. another guy who experiences the crashes had gtx 460 se, then switched to gtx 770 and vital worked fine. so it’s probably hardware plus directx combination issue. my crash log shows this:
We don’t have native directX on linux (still is used through wine, but irrelevant here), your issue is OS related if it’s tied to the swap to DirectX.
The issue that was reported here was OS and driver/vital version related, was documented, could be replicated and is fixed for now. Please open a new thread for different issues. It makes it easier for potential fix to be made. Cheers