this post was submitted on 01 Aug 2025
10 points (85.7% liked)
Linux Gaming
20383 readers
761 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:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I see you made a comment in https://github.com/ValveSoftware/gamescope/issues/1913 . Did you try vkcube like someone earlier in that issue? And the other workarounds like
--expose-wayland
?Also what version of gamescope? And you don't happen to be running steam as a flatpak do you?
EDIT: they JUST released a new version https://github.com/ValveSoftware/gamescope/compare/3.16.14...3.16.15 . So if you are having issues downgrading might be worth a try, but I haven't been able to reproduce the issues you are having.
Also, I know it sounds weird for a linux machine, but update and restart just to rule anything weird out. I've had steam and steam related applications leave around weird state, processes, etc. before and restarting is an easy way to clear that all out and start fresh, eliminating variables.
I have tried --expose-wayland. I have tried normal gamescope and u roled back to an old version. I also tried gamescope-git (I think it's called). I will retry the expose Wayland again today though with other versions as I did not do that.