8
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Sep 2025
8 points (100.0% liked)
Linux Gaming
24458 readers
28 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.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
- Linux Gaming wiki
- Gaming on Linux
- ProtonDB
- Lutris
- PCGamingWiki
- LibreGameWiki
- Boiling Steam
- Phoronix
- Linux VR Adventures
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
There are basicly two ways to go with regressions: bisecting or research.
With bisecting you restore a working backup, and try to isolate the breaking change. In your case you could try updating one package at time and testing. Since these are often GPU related, start with kernel and mesa. When you find the breaking update, you can either report it on your distros issue tracker, or git bisect it further to the breaking change in the source code to increase the change of it getting fixed quick.
With research, you look into relevant bug reporting databases. These include your distros issue tracker, Valve's issue trackers both for Steam and Proton, DXVK issue tracker, freedesktop.org and kernel issue trackers.
These are a lot of work, so most people just try random stuff. That's why you often get suggestions to do so.
Sorry I don't have an easy fix for you.