protonscr

steamui fails to launch when file descriptor limit is too high

steamopen Distro Family: NixOS
ValveSoftware/steam-for-linux#12409 · opened 2025-10-27 by michaelBelsanti · updated 2025-10-27 · 2 comments · github
MmichaelBelsanti 2025-10-27 github

Your system information

  • Steam client version: 1759461205
  • Distribution: NixOS Unstable
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: AMD

Please describe your issue in as much detail as possible:

When using a file descriptor limit of 100000, steam launches as expected. However, if I set my file descriptor limit to unlimited (ulimit -n shows 2147483584), the launch process will get stuck and the UI will never open.

This issue did not exist until a recent Steam Client update, I believe within the past week. I first raised my file descriptor limit 3 weeks ago, because the low limit was causing Deadlock to crash. Steam worked fine for a while after this, with the issue only occurring for the last few days.

Steps for reproducing this issue:

  1. Set file descriptor limit to unlimited
  2. Launch Steam
Kkisak-valve maintainer 2025-10-27 github

because the low limit was causing Deadlock to crash This would be the game hitting the hard file limit (ulimit -Hn) not, the soft file limit (ulimit -n). There's no good reason to be raising the soft file limit value, while raising the hard limit is useful.

MmichaelBelsanti 2025-10-27 github

yeah I became aware of that recently. at the time I just wanted the game to work, so I cranked the value, it definitely shouldn't be that high. thought it was worth reporting anyways in case someone else makes the same mistake, since I couldn't find error output that indicated the issue.

Nothing extracted yet.