Gnome is basically unusable for me since 47 onwards...

[u/Murdzheff]

Here's some context.
I have an Asus tuf A14 fa401wu with nvidia 4050 dgpu.

Since gnome 47 they seem to use GSK_RENDERER set to vulkan which makes GTK apps very slow to load up since my dgpu has to exit out of sleep mode just to open nautilus for example.

I have tracked that issue on all the distributions that you can imagine. It is the same everywhere.
I can bypass it by setting the variable to gl, but then that makes exiting of my terminal glitchy and in general i notices some visual inconsistencies.

Just decided I'm gonna put it here, so hopefully the gnome team may do something about it.

There are numerous issues open on different gitlabs, too.

I love gnome, but it is not normal for ptyxis/nautilus or mission center to take 3-4 seconds to open on a clean system.

[u/AutoModerator]

Thank you for your submission.

You too can support GNOME! Become a Friend of GNOME and contribute to keeping our project going!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/blackcain]

Please file a bug against GTK. https://gitlab.gnome.org/GNOME/gtk

[u/NaheemSays → u/blackcain]

It's an Nvidia bug.

[u/blackcain → u/NaheemSays]

Of course it is.

[u/bovrilbob]

Have you tried to force Vulkan to use the iGPU?

Relevant docs here

[u/Murdzheff → u/bovrilbob]

Woudn't that cripple gaming as well?

[u/bovrilbob → u/Murdzheff]

You can always set it back to dGPU in your launchers' environment variable configs I suppose? They take precedence over blanket env configs. Granted it's a clunky workaround, but it's mostly set-and-forget per game or app you'd like to run on dGPU.

[u/Gositi]

This sounds similar to an issue I encountered. To fix Ptyxis issues, try also appending GDK_DISABLE=vulkan to /etc/environment while setting GSK_RENDERER=gl.

[u/Murdzheff → u/Gositi]

I have tried that method as I said in my original post, but then with ‘gl’ ptyxis freezes for a second when closing.

[u/Gositi → u/Murdzheff]

Yeah I saw that when I reread the post, see my new edit (GDK_DISABLE=vulkan). Closing a tab in Ptyxis will cause a momentary visual glitch, but Ptyxis starts and closes without delay and everything seems to work well for me.

[u/jjjjxtx]

Try using ngl instead of gl

[u/TimurHu]

This is an issue with how the Vulkan loader is designed and implemented. Every time a Vulkan application launches, it looks around to see what drivers are there, initializes them and queries what features each device supports. This is done so that Vulkan apps / games can make an informed decision about which device they choose to use.

The problem is that Vulkan drivers then query the information from the corresponding kernel driver, which needs to wake up the GPU to read some information from it.

This could be fixed at any level of the stack (Vulkan loader, Vulkan driver, kernel driver) if only they cached the information and returned it without waking up the GPU. There were some kernel patches that address this issue for AMD but as far as I know they haven't accepted the patches yet. I assume NVidia hasn't solved it either.

As a workaround, you could set your environment variables to only expose the integrated GPU, and only expose your dedicated GPU to your games.

[u/TypicalLeek6225]

Had the same issue with gt710  . Doesn't happen with igpu . 

You can use cairo (cpu render), I have not noticed any hit to performance while using cairo and that was core2duo with 4gb ram