Closed AnErrupTion closed 3 years ago
Legendary creates all the folders in the path it writes to, given that it couldn't do that, and that writing the file fails I'm chalking this up to a permissions issue.
So based on the conversation on Discord legendary somehow ended up in a weird state where it didn't check whether or not the install directory even existed and just failed to create it again.
The initial submission here is still incorrect in the sense that the reproduction steps and erroe description are wrong, but there is an issue here that will require investigating.
Deleting the config folder ~/.config/legendary
did solve the problem.
With commit 74bc2fecc0dba9349b5dfe1f598914a129c3c169 attempting to start an installation if the conditions causing this issue are present (game folder deleted, but not uninstalled) will show an error and abort.
Platform
Operating system and version: Arch Linux Legendary version (
legendary -V
):legendary version "0.20.14", codename "Nova Prospekt"
Expected Behavior
Games should install properly and I should not have to create the
~/legendary
folder.Current Behavior
When trying to install a game (here Rocket League, but should apply to any game), I first get an error telling me that the
legendary
folder in my home directory is not present. I find it weird that legendary didn't create it itself, so I did it. After that, when I try again, the game downloads, but the FileWorker always gives me errors that the files of the game can't be written to disk. Here is an example message:Steps to Reproduce
legendary install Sugar
Additional information
My SSD is fine, I can write files and directories to it, and this issue never happened before.