Latest Gnome apps not working in fedora 41 using wayland

Ask Fedora
, , ,
21

I used the software center in GNOME and installed v. 560.35.03. I just followed the instructions in Gnome.

Fortunately I had enabled SSH so I could connect to the machine and set this in my environment: GSK_RENDERER = ngl

Seems to be working now.

Out of curiosity, how did you install your drivers that seems to be working well?

22

I followed the RPM Fusion instructions for Nvidia drivers.

23

Thanks. Okay, I usually do that but got curious since Fedora 41 re-introduced the drivers in the software center.

24

Not true for most.
Simply edit the file /etc/environment and add a line reading
GSK_RENDERER=ngl then log out and back in (or reboot).
It may be necessary to replace ‘ngl’ wih ‘gl’ if you have an older gpu.

25

how to edit if terminal or apps wont open to edit??? i just had this and nope cant edit or do anything

26

  1. Boot to a live usb media and edit the file from there. The nvidia drivers will not be loaded but you can still use the system to make recovery.

  2. Most can boot to a text environment by using the grub menu and editing the commands there.
    On the line beginning with linux= remove the rhgb quiet and replace it with 3

  3. You also can force a boot without using the nvidia drivers by editing the same line and removing the 2 blacklist options rd.driver.blacklist=nouveau modprobe.blacklist=nouveau so the nouveau drivers are loaded first and the nvidia drivers are ignored

1 Like
27
  1. Switch to a VT (ctrl + alt + f3), login and use vi, nano or whatever to edit
4 Likes
28

I change /etc/environment with GSK_RENDERER = gl and all ok for me. Thanks

1 Like
29

Great advice. Thanks! And for those curious, ctrl+alt+f2 to switch back. :slight_smile: (at least worked for me)

30

Can we expect the actual fix from devs anytime soon? Is there a link to this issue?
I found this in that archlinux forum but its closed.

31

It’s a bug in Nvidia drivers. Update Nvidia drivers to version 565 or greater to fix the issue.

1 Like
32

I bricked my system even 565 drivers had to remove Mok key to get back to system since no terminal or nothing opened so it is more than Nvidia driver bug all works fine with nouveau and mesa just happened like week ago when testing

33

Thanks! It worked. It was Nvidia after all, the usual suspect. At one point, I was convinced its not them.
Need to update the solution to the question.

34

Hi People,
This problem was resolved. It’s necessary change content of environment file on etc;

Now I have other issue GDM 47 do not open others WM that are using X.org. example 9wm or Window Maker.

Regards.
Emerson Colchesqui

36

When using bash as your shell those line should not contain spaces. It should instead be GSK_RENDERER=gl

1 Like
37

To apply these fixes you can switch to the x11 session, or open a VT using ctrl + alt + f3

1

Add GSK_RENDERER=gl (GSK_RENDERER=ngl also works on better hardware) in /etc/environment and after saving the file, reboot the pc ( just logging out should work too ).

https://bbs.archlinux.org/viewtopic.php?id=299546

Thanks to the discord channel members for the solutions!

2

38

/etc/enviroment has typo should be /etc/environment

1 Like
39

What’s more-preferred between /etc/environment and /etc/profile.d? I use profile.d.

40

/etc/environment is a system-wide configuration file used to set up environment variables, whereas /etc/profile.d/*.sh are global initialization scripts. That’s why in the latter case you need to use the EXPORT command, but not in the former.

41

Either works, but the timing on when they are used and the scope of affect is different.

Files in /etc/profile.d/ are sourced when the user logs in and are implemented for the users environment only.
The /etc/environment file is system wide with global effect for all users as already noted. It is activated when the system is booted.