search

ublue-os / bazzite

Bazzite is a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
https://bazzite.gg
Apache License 2.0
4.1k stars 250 forks source link

Some GTK apps do not launch #1732

Open aaron1857 opened 1 month ago

aaron1857 commented 1 month ago

Describe the bug

Some gtk apps seem to crash when trying to launch them. The apps do not open at all.

Below is an output when trying to launch flatseal from the command line.

flatpak run com.github.tchx84.Flatseal 

** (process:40516): WARNING **: 15:42:33.210: Error writing credentials to socket: Error sending message: Broken pipe

(com.github.tchx84.Flatseal:2): Gtk-WARNING **: 15:42:33.338: Unknown key gtk-modules in /home/aaron/.var/app/com.github.tchx84.Flatseal/config/gtk-4.0/settings.ini

(com.github.tchx84.Flatseal:2): Adwaita-WARNING **: 15:42:33.395: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Gdk-Message: 15:42:33.911: Error 71 (Protocol error) dispatching to Wayland display.

This does not impact every app. I'll list some apps that work normally and some that do not launch. These are apps I have on my system, I am willing to install and test other things if needed. Apps that do work:

Apps that do not work

EDIT: I removed Speech Note from the apps that don't work list since it does work. Furthermore, upon launching I realised it is not a gtk app.

What did you expect to happen?

I expected to open the app normally.

Output of rpm-ostree status

rpm-ostree status State: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:latest Digest: sha256:f0a715ec44064ebfa14504db0c72b3790542ce3bcd3d7f3b9fb068e6a04197e7 Version: 40.20240930.0 (2024-09-30T15:25:37Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:latest Digest: sha256:7714620ce66e84806949720204c07da491b6b31bc6304a27ca620893bf1508b9 Version: 40.20240922.0 (2024-09-23T05:09:18Z)

Hardware

I am using a Dell 5515 laptop. It has an NVIDIA GeForce RTX 3050 Ti Mobile GPU with an AMD integrated GPU.

Here is the Dell listing that contains the exact specifications. https://www.dell.com/en-us/shop/dell-laptops-and-notebooks/new-dell-g15-ryzen-gaming-laptop/spd/g-series-15-5515-laptop/cag155w10p1c2100pa

Extra information or context

I believe this issue has been going on for a while, but I could properly investigate it earlier due to a lack of time. I have previously used Otto and Vapor themes in KDE settings, but I currently am on the Breeze Dark theme.

I have looked at this Reddit post. As a result, I tried removing gtk-application-prefer-dark-theme=true in /var/home/aaron/.config/gtk-4.0/settings.ini but that did not work.

I even tried completely removing the gtk-4.0 folder and then reselecting the Breeze Light and then Breeze Dark theme in KDE settings to hopefully reset the settings to the default value. This did not work either.

I've decided not to mess with it further to avoid further messing something up.

Sgaytor commented 1 month ago

This is a known issue with the latest gnome 47 runtime which launches apps using the vulkan renderer by default. It seems to cause issues on systems with an iGPU + nvidia dGPU like yours.

The work-around for now is to set an environment variable which forces the use of the previous open-gl renderer: mkdir -p ~/.config/environment.d && echo "GSK_RENDERER=ngl" >> ~/.config/environment.d/gsk.conf

You should make a note somewhere to remind yourself that you should remove this later when the issue is fixed so you can enjoy the performance improvements from the vulkan renderer!

aaron1857 commented 1 month ago

Ok, I'll try that solution for now. I couldn't find information on this online, but perhaps that was due to my lack of ability in finding out what was wrong.

Is there any way for me to know when the issue would be fixed so I remove the environment variable?

Thanks for the help!

Sgaytor commented 1 month ago

So it seems it's a bug with the proprietary nvidia drivers, but it looks like you're running the open drivers. Of course it's entirely possible that the open drivers have the same behavior that's causing the issue.

rpm-ostree status State: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:latest Digest: sha256:f0a715ec44064ebfa14504db0c72b3790542ce3bcd3d7f3b9fb068e6a04197e7 Version: 40.20240930.0 (2024-09-30T15:25:37Z)

A good place to start would be the issue trackers at redhat, mesa, and wayland however on a quick skim I didn't see anything about the open nvidia drivers. I found decent search results by searching "Error 71 (Protocol error) dispatching to Wayland display" and filtering by the last month, that might point you in the right direction.

Apart from that you can always just experiment with removing the environment variable from ~/.config/environment.d/gsk.conf with each new update and see if it works yet.