Temporary path is reported as having 0 bytes free

[LukeShortCloud]

On Arch Linux based systems (including Manjaro), the /tmp/ directory is mounted as an ephemeral file system tmpfs. I have forced it to use ramfs on my system (the difference being that no swap is ever used). This creates an issue when using ge-install-manager. It reports a false-positive about me not having enough storage space.

$ ge-install-manager -i Proton-6.5-GE-2
WARNING: Not enough free space on temp_path: /tmp
Need at least 335686163 bytes but there is only 0 bytes free
Free up space or change temp_path in the configuration file
Version 6.5-GE-2 not found

As a workaround, I have changed the tmp_path in the ~/.config/ge-install-manager/ge-install-manager.conf configuration file to a location on my home partition.

[toazd]

How exactly have you forced your system to use ramfs? I will need to reproduce the issue myself to find a proper solution that works for as many use cases as possible.

A potentially more simple solution would be to remove the check entirely since the system will already throw an error if there isn't enough freespace available. This space check was originally intended to avoid having fragments of files laying around if an install failed but since then I have also greatly simplified where the various configuration and temporary files are stored and how they are removed during cleanup or uninstall. So, it's not really necessary anymore. However, if you are still available to provide details I would like to learn why this issue occurred in the first place.

For reference, the function used (SpaceRemaining) to determine the remaining free space is on lines 2972-2999 of the script.

[LukeShortCloud]

Hey @toazd , thanks for your help with the few GitHub issues I've opened. It's really appreciated and you've got an awesome project here.

Here is an example command for mounting ramfs onto the /mnt directory. That will only use RAM. Alternatively, tmpfs can be used which also includes swap.

$ sudo mount ramfs -t ramfs /mnt

[toazd]

Using the information you provided I am not able to reproduce the same issue on Arch linux. I will need more details about what changes you have made to force your system to use only ramfs.