{"UUID":"dc2df2ab-1c9d-4e02-9368-31be29f747bf","URL":"https://github.com/valvesoftware/steam-for-linux/issues/3671","ArchiveURL":"","Title":"Steam client recursively deleted user files on Linux","StartTime":"0001-01-01T00:00:00Z","EndTime":"0001-01-01T00:00:00Z","Categories":["cloud","config-change"],"Keywords":["steam","linux","ubuntu","file deletion","data loss","symlink","bug"],"Company":"Valve","Product":"Steam","SourcePublishedAt":"2015-01-14T23:28:17Z","SourceFetchedAt":"2026-05-04T17:54:10.95792Z","Summary":"Steam's desktop client deleted all local files and directories. The thing I find most interesting about this is that, after this blew up on social media, there were widespread reports that this was reported to Valve months earlier. But Valve doesn't triage most bugs, resulting in an extremely long time-to-mitigate, despite having multiple bug reports on this issue.","Description":"On or before January 14, 2015, a Steam user on Ubuntu 14.04 encountered a critical bug. After moving the `~/.local/share/steam` directory to an external drive and creating a symlink to the new location, launching the Steam client resulted in the recursive deletion of all files owned by the user, starting from the root directory.\n\nThe underlying cause appears to be a flaw in a Steam script that handles directory changes. The user described the script's behavior as \"really, really stupid,\" suggesting it incorrectly interpreted the symlinked path, leading to an unintended and destructive recursive deletion operation across the entire file system accessible to the user.\n\nThe incident led to significant data loss for the affected user, including files on a 3TB external backup drive mounted under `/media`. While the user had cloud backups, mitigating a complete disaster, the event was characterized as \"a huge hassle\" due to the extensive data loss.\n\nThe article, being an initial bug report, does not detail any immediate remediation steps taken by Valve. However, the user suggested that Steam should either throw an error when encountering such a configuration or provide an option for users to select an installation directory, similar to its Windows counterpart, to prevent similar incidents."}