You are not logged in.
As the title says, applications from gnome 47 doesn't launch untill vulkan-intel is uninstalled. This wasn't happening in gnome 46, although gnome launches fine from gdm I couldn't even open gnome-console I had to switch tty to install alacritty and launch gnome-control-centre but I got this error:
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
After removing vulkan-intel the issue was solved. But why??
Last edited by Ayu2805 (2024-09-19 16:07:18)
Offline
Same issue here. Launching GNOME programs with GSK_RENDERER=ngl also seems to work around the problem. So this appears to be something to do with the vulkan implementation.
Offline
Launching GNOME programs with GSK_RENDERER=ngl also seems to work around the problem.
I see, welp I either way I don't want to launch something from terminal everytime hence I choose to uninstall vulkan-intel for now.
Offline
You can set that environment globally. What's your actual GPU? If it has "limping along" level of Vulkan support that could explain it, if it's vulkan support is in theory available and not completely broken and this just a GTK bug, setting that environment variable will fix it without leaving you stranded should you ever actually want to use Vulkan.
Offline
You can set that environment globally.
I see, okay.
What's your actual GPU?
GTX 1650, running NVIDIA Open 560
Offline
There seems to be some discussion on the GNOME gitlab about this problem:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3664
As usual, fingers pointing to nvidia driver problems. I'm not sure there is any resolution at the moment.
Offline
There seems to be some discussion on the GNOME gitlab about this problem:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3664
I see, I hope it gets fixed.
As usual, fingers pointing to nvidia driver problems. I'm not sure there is any resolution at the moment.
But it wasn't a problem in Gnome 46. Is it the issue with proprietary NVIDIA drivers too?
Last edited by Ayu2805 (2024-09-19 17:33:03)
Offline
But it wasn't a problem in Gnome 46. Is it the issue with proprietary NVIDIA drivers too?
It's an issue now because Gnome 47 switched to using vulkan to render by default. This is why setting the GSK_RENDERER=ngl works, as it disabled the vulkan renderer.
Not ideal, but at least makes a usable system.
Offline
It's an issue now because Gnome 47 switched to using vulkan to render by default. This is why setting the GSK_RENDERER=ngl works, as it disabled the vulkan renderer.
Not ideal, but at least makes a usable system.
I see, okay. I'll do that for now.
Offline
In my personal opinion, I don't think this is really an issue. I think you can try following the tutorial on ArchWiki to correctly set the MESA_VK_DEVICE_SELECT environment variable to your discrete graphics card device. I think this should solve the problem.
Offline
While it would, you definitely don't want to start the GPU for random desktop application #4 that the integrated GPU would be more than sufficient for.
Offline
```
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
```
I wrote this piece of Intel driver code in 2020. At that time, this feature was very low priority for YUV formats, so I decided to return to it when there was a realworld use case for it. And here we are.
> After removing vulkan-intel the issue was solved. But why??
The apps you were running were unintentionally choosing to use the Intel Vulkan driver. I assume the GTK libraries were merely choosing the first working Vulkan driver it found during driver enumeration. After removing vulkan-intel, some other Vulkan driver became the first during driver enumeration.
For all the Arch users who are using machines with just an Intel gpu installed, I'll file a bug against the Intel driver and encourage Intel to investigate.
Offline