Hey guys, not sure what happened or if I installed something wrong but some of my applications like Firefox (flatpak) and gnome-control-center are just showing as blank when I open them. If I select them from overview, it stays as blank and can’t select anything from it. This issue doesn’t happen on all gnome/flatpak apps.
Any idea how can I troubleshoot this further?
Im on Fedora SilverBlue 37
EDIT: upgraded to 38, but same issue. Posted in AskFedora - https://discussion.fedoraproject.org/t/some-apps-are-just-blank-and-unusable/85600
Set the environment variable MOZ_ENABLE_WAYLAND=1
thanks, but i already tried it
Can you run an rpm-ostree status and paste the results here?
Might also be good to post in ask fedora if you haven’t already.
The people who maintain silverblue are often there to help out.
Ahhh I see. Might be an issue with the Nvidia drivers and Wayland.
I would try the following in order and see if any of them fixes it:
-
Update your system “
rpm-ostree update” and reboot -
Make sure you are on a Wayland session. This also provides instructions to see what apps are in X11 mode (which I suspect Firefox and Software Center are in your case).
-
2.1 If you are already on Wayland (its the default in Fedora 37): Install Flatseal and force Wayland for Firefox (toggle off X11 and ‘Fallback to X11’)
-
2.2 If you are on X11, logout and switch to Wayland in the login screen and follow 2.1 to force Firefox to Wayland.
-
If that doesn’t work I would follow these specific steps to install Nvidia on silverblue. RPM Fusion also has some specific guides for Silverblue that you should check to see if you missed a step.
-
I would also consider upgrading to Fedora 38, and bump up your RPM fusion major version to track Fedora 38.
I always use Wayland and already installed nvidia drivers. Upgrading now to 38, will update later
Update: same issue after upgrading to F38
posted in ask fedora - https://discussion.fedoraproject.org/t/some-apps-are-just-blank-and-unusable/85600
-
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
