this post was submitted on 25 Apr 2025
27 points (100.0% liked)

Linux Gaming

18081 readers
163 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
 

I've had a problem in several games, and I don't really no where to to being debugging it. It's not like there is any error message. Is it my DE? my distro? drivers? proton? the game engine itself?

I've done some basic web searches, and all of the answers are hyper specific, or "alt-tab just breaks some times".

The actual problem: When I alt-tab, some games will appear to freeze when I tab back in. I've noticed that while I am holding alt-tab and have a non-game window selected, the game is not frozen. As long as have not selected the window I am trying to swap to, it keeps running. It's almost as if the game has inverted it's internal state of whether it's in the foreground are not.

(if it does matter, I am using Gnome on 22.04 PopOS, Nvidia 565 driver, Steam/Proton).

top 9 comments
sorted by: hot top controversial new old
[–] Max_P@lemmy.max-p.me 1 points 6 hours ago

Not an explanation or proper fix, but running the games through Gamescope might fix it by side effect. In gamescope the game would never lose focus and so shouldn't have problems resuming afterwards.

[–] over_clox@lemmy.world 14 points 17 hours ago (2 children)

Disclaimer: Theory, based loosely on related experiences in Windows ages ago back when I actually used Windows.

The keyboard handler might be getting confused when you Alt+Tab, leaving the game stuck thinking you're still holding Alt+Tab when you return to the game.

Just for shits and giggles, the next time you experience this, try tapping Alt once or twice to see if that refreshes the keyboard buffer and status.

You might even try tapping the other toggle/special keys as well, such as Ctrl, Shift, Esc...

I realize Windows and Linux are like comparing bananas to oranges, but still, the keyboard buffer might not be getting refreshed properly when switching apps.

It's worth a try, do let us know if this helps in any way.

[–] secret300@lemmy.sdf.org 8 points 16 hours ago

This has happened to me when playing older games on Linux

[–] Brewchin@lemmy.world 2 points 12 hours ago

Sounds plausible.

FWIW, New World (doesn't have borderless fullscreen) got me into the habit of tapping the Windows key before doing anything outside the game. Other than when the game is starting, it never has any problems when I do that.

I'm using EndeavourOS, KDE, Wayland, so YMMV.

[–] Lemmchen@feddit.org 1 points 11 hours ago

sudo dmesg -Tw

[–] superglue@lemmy.dbzer0.com 3 points 16 hours ago

Try opening the Nvidia control panel, turn off Force Composition Pipeline. I had this same issue.

[–] Lojcs@lemm.ee 3 points 17 hours ago* (last edited 17 hours ago)

Might be game specific. I don't know how to solve the issue but maybe you could try opening the game in a different virtual desktop and switching desktops and see if that causes it. Or press the meta key and see if that causes it too

[–] slimerancher@lemmy.world 2 points 17 hours ago

Most probably graphics / nividia issue. But not a general issue, related to the configuration or hardware or something.

For most such cases when you can't figure out anything, it's generally a good idea to ask in your distro's support forum. There are people who can usually help you debug a few things. It doesn't always solve your problem, but you can get some possible pointers.

[–] cmnybo@discuss.tchncs.de 1 points 15 hours ago

It could be a game issue. I remember a lot of games had issues with alt-tabbing back when I used windows. It could also be a Wine issue. I had one game that started freezing when alt-tabbing after a Wine update a couple months ago. Rolling back to the previous version fixed it.