I’m a Fedora 42 KDE user who had experienced a bug three days ago after the recent update that installed the new Mesa drivers. A number of the apps that I use daily, such as Vesktop, Session, Element, FreeTube fail to launch, and if they do (after the configuration of their settings in flatseal, namely, turning on X11 socket for Vesktop) they would launch but with a completely blank window. I ran flatpak run dev.vencord.Vesktop to see what errors are logged and it returned the following
Running on native Wayland Passing the followng arguments to Electron: --enable-speech-dispatcher --ozone-platform-hint=auto --enable-wayland-ime --wayland-text-input-version=3 [3:0608/082922.124673:ERROR:bus.co(400)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such fileor directory MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER).
(x11 is turned off by me from flatseal because I don’t need it for Vesktop)
The Mesa error here is what I believe to be at stake.
So I figured out a workaround to manually run an erring app from the terminal, by installing org.freedesktop.Platform.GL.default/x86_64/23.08 (flatpak install org.freedesktop.Platform.GL.default/x86_64/23.08) and then running FLATPAK_GL_DRIVERS=25.0.5 flatpak run dev.vencord.Vesktop, an older mesa version. It worked but at the expense of convenience. Problem is, I do not wish to permanently run apps through the terminal each time I want to use it, nor do I want to go to the extent of modifying the .desktop files and force them to run with an older version of Mesa. It is worth to mention that not all flatpaks apps run through this bug, as Librewolf browser is installed from flathub and I can run it all right. Let me know if this is the proper place to report this bug, because I heard I’m better off reporting it to Feedesktop SDK Project.
