Steam's Linux Update Mechanism: Users Call Out Forced Manual Triggers and Bloat Updates
Linux gamers report that Steam fails to notify them proactively when games require updates. Users must manually launch the game to force the update process to begin.
The sentiment is overwhelmingly negative. Users like john89 criticize the system's design, noting the complete absence of proactive updates. They specifically point to massive, recurring update demands, citing Skyrim's repeated 1GB+ patches even after gameplay. The critique extends to questioning the overall utility of Steam on Linux, suggesting the platform itself impedes the free software ecosystem.
The consensus is that Steam’s game update handling on Linux is profoundly inefficient. The fault line exists between the user expectation of a reliable, seamless update pipeline and the platform’s observable technical failure rate, which is perceived as intentionally burdensome.
Key Points
Steam requires manual game launches to initiate updates on Linux.
john89 asserts there is no proactive notification system; users are forced to trigger updates themselves.
Updates are excessively large and seem unnecessary.
john89 cited Skyrim demanding massive, repetitive updates (1GB+) even when the game is clearly functional.
The platform is hindering the free software movement.
john89 made a broad critical assessment, arguing Steam acts as an obstacle to the open-source ecosystem.
The update mechanism is fundamentally flawed on Linux.
john89 scored the overall handling of updates as having 'major inefficiencies,' indicating widespread dissatisfaction.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.