> There are too many apps that hardcoded IPv4 in their code
That would work over CLAT, which most operating systems support. Steam has this issue, clat works around it while still using a ipv6-only net.
https://github.com/ValveSoftware/steam-for-linux/issues/3372...
In IPv6 traffic crosses the 50% markValveSoftware
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
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
- mrmeee/bumblebee-old-and-abbandoned · linked in 2 of the same 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, 1:49:46 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.
* 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 7 | 2 | 5 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 3 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 12 | 0 | 12 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
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 GitHubWhat Hacker News says
71 sourcesAfter many years playing on Linux, first struggling with Wine then with Proton when it came out, had to install Windows on my gaming pc. I mostly play Overwatch 2 with friends on my very short free time, thanks to a Steam bug (https://github.com/ValveSoftware/steam-for-linux/issues/1028...), on every single evening I had to wait forever (seriously, 15+ min) for shaders to compile or start the game immediately but suffer on every match beginning (different map) with stuttering.
That’s a deal breaker for me, I tried a fresh Bazzite install (from Arch) before giving up, exact same issue.
I wish Valve comes around one day and fixes that, I’ll kick Windows out of life in a heartbeat.
In Linux gamers on Steam cross over the 3% markValve has done an amazing job turning Linux gaming a reality, I really admire their efforts. Unfortunately I had to switch back to Windows on my gaming rig due to a Steam bug which unnecessarily downloads the shader cache of several game every single day, disabling the cache hurts the performance. That’s been plaguing many users for years and surprisingly Valve hasn’t fixed it: https://github.com/ValveSoftware/steam-for-linux/issues/1028...
In Games run faster on SteamOS than Windows 11, Ars testing findsThe time Steam deleted someone's home directory
1 points · Open discussionTo raise awareness: there's been a bug with the Linux Steam client which has been persistent for a long time.
TL;DR: if you have Steam running for more than a ~day or so, you will run out of window handles so you won't be able to open any new graphical application/window until you restart Steam.
Using Steam Chat appears to make the issue worse (it happens earlier).
This has been documented under https://github.com/ValveSoftware/steam-for-linux/issues/9094 but for some reason that issue has been closed.
I personally just restart Steam every day but if someone else encounters this issue and doesn't know why their windows are not opening, this is why :)
I am using KDE/Wayland but I've observed this under X11 too.
In Improving Steam Client Stability on LinuxIt happens to the best of us
https://github.com/ValveSoftware/steam-for-linux/issues/3671
In Techniques I use to create a great user experience for shell scriptsThis 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 3am while half their brain is still sleeping) and b) accessible over ssh because we have secure ssh access to these envs but ~nothing else.
So I love TUIs.
That said, I'm always a little puzzled about why people build these libraries in bash. Is it simply curiosity? Maybe, and if so, godspeed.
But if it's driven by pragmatism, let me assure the reader that if there are limits to the extents I will go to get python somewhere instead of writing even a somewhat nontrivial bash script, I have yet to find them. Not only is bash just kind of really annoying to program in, it's also nearly unethical to program in. Let me link the 2 I always link to when someone tells me they
Read the rest
're "working on" a bash script.
Steam deleted my entire system (empty variable expansion): https://github.com/valvesoftware/steam-for-linux/issues/3671
Bumblebee deletes /usr due to space: https://www.reddit.com/r/softwaregore/comments/2hsdo6/giant_...
So I warn people: if you use python, you'll categorically avoid being the third entry in my list.
> The whole situation reminds me of the Steam uninstaller, where a single space had some remarkable results.
https://github.com/valvesoftware/steam-for-linux/issues/3671
In Hacked – Installed a global KDE Plasma theme – it erased all my drivesSteam ignores the "Later" button on client updates
6 points · Open discussionrm -rf $INSTALL_DIR/*
this line of code has at least two gotchas. if you run it to test it out, there is a good chance you will destroy your data. It is otherwise a valid line of code.
This is not a theoretical problem: https://github.com/valvesoftware/steam-for-linux/issues/3671
In Moderation Strike: Results of Negotiations> You can find many issue threads on GitHub reporting client freezes and crashes.
The fact that these are happening does not necessarily mean the client is getting worse. For example, it could mean that more people are installing Steam for Linux. There is no baseline to say it's getting worse, because nobody opens an issue saying "all working here."
In my experience, the only issue I have on Wayland is this: https://github.com/ValveSoftware/steam-for-linux/issues/7245 (workaround: disable animated avatars) (edit: all AMD machine)
> outside of Steam Deck ofc
There is nothing special about the Steam Deck. It's just another Linux machine.
> TF2
I don't play any Source games, but I could see TF2 having issues because it's in maintenance mode. If it is bjorked that has nothing to do with Steam.
In Fedora 38 LLVM vs. Team Fortress 2Right, though I vaguely remember that I had tried the pressure-vessel-based sandboxing a long time ago and it didn't work if Steam itself was inside a container. https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/i... seems familiar.
(Why do I insist on running Steam inside a container? Because there's no way I'll trust it on my actual filesystem after https://github.com/ValveSoftware/steam-for-linux/issues/3671 )
In Wine 8.1My main qualms with bash as a scripting language are that its syntax is not only kind of bonkers (no judgement, I know it's an old tool) but also just crazily unsafe. I link to a few high-profile things whenever people ask me why my mantra is "the time to switch your script from bash to python is when you want to delete things".
>rm -rf /usr /lib/nvidia-current/xorg/xorg
https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi...
>rm -rf "$STEAMROOT/"*
https://github.com/valvesoftware/steam-for-linux/issues/3671
It's just too easy to shoot your foot.
In Ask HN: What are the best tools for web scraping in 2022?Since no one has said it yet, please always use https://www.shellcheck.net/ on your scripts, you don't want to be That Guy https://github.com/ValveSoftware/steam-for-linux/issues/3671
In Type-ish – A runtime type checker for bash, in bash> Problems like removing a large directory instead of a file
rm doens't do that unless you explicitly tell it to.
> Problems like removing a large directory instead of a file, creating your files on random places instead of the directory you pass on, or creating more files than you intended?
But yes, all of these can and do exist in other languages. Using python as an example, if you read an environment variable without checking it's set (as in the infamous steam bug) [0], you'll end up with pretty much the exact same behaviour. You can misindent your loop in python and not create/remove files that you intend to, or your script can have a syntax error halfway through and the interpreter will happily proceed until it halts, and leave you in a half baked state just like bash does.
[0] https://github.com/valvesoftware/steam-for-linux/issues
Read the rest
Showing the 15 most recent of 71 sources. Enable JavaScript to search and browse every indexed mention.