this post was submitted on 04 Sep 2024
7 points (73.3% liked)

Linux Gaming

14944 readers
73 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
monolalia@lemmy.world
7
Way to stay on Nvidia 550 w/ Fedora 40? (lemmy.today)
submitted 1 week ago by biptoot@lemmy.today to c/linux_gaming@lemmy.world
15 comments fedilink hide all child comments
 

Been running Fedora 40 for a few months, and having a hard time keeping Wayland as the desktop environment. Just did a fresh install, and the Nvidia driver updates to 555.58.02. I really want to stick with the Recommended branch, not the New Feature branch. Every update, Wayland breaks. How do I rollback to 550, and switch to the Recommended Branch for updates?

you are viewing a single comment's thread
view the rest of the comments
[–] Lojcs@lemm.ee 6 points 1 week ago (1 children)

Every update, Wayland breaks

Would you elaborate? If anything 555 and 560 should be more stable on Wayland

[–] biptoot@lemmy.today 2 points 1 week ago* (last edited 1 week ago)

Yes, and thank you for your interest in helping. Appreciated! After an update, I will eventually reboot. When doing so, the options in the gear at the Gnome login will be

  • Gnome
  • Gnome Classic

Both of these options are X11. I verify this with $ echo $XDG_SESSION_TYPE and see X11. When Wayland is working, the Gnome login will show four session types:

  • Gnome
  • Gnome Classic
  • Gnome on X.org
  • Gnome Classic on X.org

I haven't been able to locate a log file where something looks relevant to the decision made at boot for XDG, Wayland, or X11 that chooses one over the other. It's just as though Wayland stops being an option. 3 or 4 updates later, I'll have Wayland back again - but no idea why it comes and goes. My caveman intuition tells me it happens around nvidia updates, but I haven't kept strict notes on that.