HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ValveSoftware
steam-for-linux
Systems & Infrastructure2012–2026
ValveSoftware / steam-for-linux

steam-for-linux

Issue tracking for the Steam for Linux beta client

63Distinct people
71Mentions
2Explicit recommenders
4.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Issue tracking for the Steam for Linux beta client

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

This is cool, I've used curses UIs to build various small things that need to be a) vaguely easy to use (so, complicated CLIs are out. oncalls need to be able to use this at…

atomicnumber3 used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year71 dated mentions

Observed mentions: 2012-12-20 00:27:43 UTC to 2026-04-16 20:26:26 UTC.

0369122012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC101
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC817
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC707
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC725
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC835
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC12012
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC707
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Steam for Linux Client This is the README for the Steam for Linux client. Hardware and Software Requirements Steam for Linux stable client requirements are as follows: OS: Latest Ubuntu or Ubuntu LTS with a 64-bit (x86_64, AMD64) Linux kernel Older Ubuntu LTS branches are not supported and may stop working in a future Steam release, especially the branches in ESM status (Ubuntu 18.04 or older). Processor: 1GHz Pentium 4 or AMD Opteron equivalent or better Any x86_64 / AMD64 CPU with support for the CMPXCHG16B and SSE3 instruction sets Memory: 512 MB RAM Graphics: Any NVIDIA / AMD / Intel Requires latest 64-bit (x86_64, AMD64) and 32-bit (i386, IA32) graphics drivers. Install them using sudo ubuntu-drivers autoinstall. Storage: 5 GB available space Additional Notes: Requires internet connection for initial installation Requires 64-bit (x86_64, AMD64) and 32-bit (i386, IA32) glibc Starting from 2025-08-15, glibc 2.31 or newer will be required. This affects users of older distributions such as Debian 10, RHEL/CentOS 8, Slackware 14.x, Ubuntu 18.04. For a list of requirements for the current beta client, please see README.beta.md Getting Started Install Steam for Linux client: Download the steam_latest.deb package from this location. Navigate to the directory containing steam_latest.deb and double-click it. This launches Ubuntu Software Center and installs the package. If you prefer to install from the command-line, use gdebi. Install the gdebi-core package (apt install gdebi-core) and then install the Steam for Linux package (gdebi steam_latest.deb). For a list of games supported by Steam for Linux either visit this page or click Store (from the client) and then the Linux tab on the far-right. We recommend that you join the Steam for Linux official game group, located here. You will find future beta announcements and other information posted here as well as an active discussion forum. Reporting Issues If you encounter an issue with Steam for Linux, first search the issue list to see if it has already been reported. Include closed issues in your search. For issues with: Source-based games (HL2:DM, HL2, HL2:EP1, HL2:EP2, TF2, DoD:S, CS:S), visit our Source Issue List GoldSrc-based games (HL, HL:BS, HL:OF, TFC, DoD, DMC, CS, CS:CZ or Ricochet), visit our Half-Life Issue List Portal 2, visit our Portal 2 Issue List CS:GO, visit our CS:GO Issue List Games using Proton, visit our Proton Issue List If it has not been reported, create a new issue with the following information: a short, descriptive title; a detailed description of the issue, including any output from the command line; steps for reproducing the issue; and your system information. Please place logs either in a code block (go here for a GFM cheat sheet) or a gist. When possible, please include a differential between a working configuration and the reported issue. If a crash is involved, please include any CrashIDs or minidumps related to the issue in an archive. Archives can be drag and dropped into the text box of github. For tracking purposes, there should be one issue per issue report. System Information System information can be gathered from within steam (Help -> System Information). Once your information appears: right-click within the dialog, choose Select All, right-click again, and then choose Copy. Paste this information into a gist and include a link to it from your bug report. Conduct There are basic rules of conduct that should be followed at all times by everyone participating in the discussions. While this is generally a relaxed environment, please remember the following: Do not insult, harass, or demean anyone. Do not intentionally multi-post an issue. Do not use ALL CAPS when creating an issue report. Do not repeatedly update an open issue remarking that the issue persists. Remember: Just because the issue you reported was reported here does not mean that it is an issue with Steam. Also, should your issue not be resolved immediately, it does not mean that a resolution is not being researched or tested. Patience is always appreciated.
Read the full README on GitHub

What Hacker News says

7 sources
I believe in the value of this project, OP (lihaoyi). Your example of https://github.com/valvesoftware/steam-for-linux/issues/3671 and rm -rf "$STEAMROOT/"* erasing everything when $STEAMROOT is a blank string are spot on. I remember spending a couple of hours one weekend getting this to work in Cygwin. I lost energy to pursue it further after getting it to work, which is typical with me :-) (Then I revisit things after 6 months or so, with some luck and free time). Anyway, here are my notes from that attempt, in case someone else runs into the same issues: a) I fixed the height and width in ammonite/repl/FrontEndUtils.scala so that it doesn’t go down the hell hole of Cygwin tput and tty issues b) hard-coded repl.frontEnd() = ammonite.repl.FrontEnd.JLineUnix in ammonite/shell/Configure.scala c) sbt '~shell/test:run' to run the fully-loade
Read the rest
d REPL
In Ammonite: Scala Scripting
Steam does a good job of covering all of the Linux distros, even if you're on your own for things like Arch Linux (the community maintains a great Wiki). The only thing they need to do is fix high-DPI display support (it's broken even on Windows and there is a HUGE issue on GitHub that has been around for years now without any action being taken to resolve it, a little frustrating): https://github.com/ValveSoftware/steam-for-linux/issues/3492
In Nvidia's Hackintosh Support Is an Insurgency Against Apple's Computers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.