this post was submitted on 30 Nov 2025
48 points (98.0% liked)

Linux Gaming

22296 readers
209 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'm using Arch currently and the following issues have been present on every install of Steam I've had:

  • Controller inputs break constantly. If I use big picture mode, the games will be in some quasi state where it both detects my controller and doesn't.
  • The menus take like 3 seconds to open.
  • The right click menu in the system tray does not work 30% of the time.
  • Worst of all, when I close a game, steam will not detect that it closes. Once this happens, no other page will load, no menus will open, and i have to killall steam -s SIGKILL, since no other signal works. It's also survived SIGKILL multiple times. How?
  • In game, the shift+tab menu does not work; half the buttons are unresponsive and the game will crash upon closing shift+tab

The arch wiki had nothing on this.

Flatpak and native installs have the same problem, reinstallation does nothing, steam --reset does nothing.

These issues occur across multiple games with different engines.

It's very strange since I have a very generic system and most people seem to have great experiences.

you are viewing a single comment's thread
view the rest of the comments
[–] de_lancre@lemmy.world 1 points 18 hours ago

I had all those issues on arch for a while, but recent (this week) update indeed seems to bork something even more. Not sure if it was steam update or arch os update, but currently steam window have 50/50 chance to become laggy af and unresponsive. Basically making it unusable. Closing to tray and opening again can fix it with same 50/50 chance.

Have no clue how to fix it. Check their github, maybe someone already reported a bug.