Bazzite AppImage Saying No Storage Space

[simmonsil]

I am running Bazzite 44 and I have successfully loaded in the books into the app, but whenever I click Liberate to download them, the app tells me that I do not have enough free space. Its saying I have 0 MB free. I have tried different directories and it seems to continue to run into the same issue.

I tried running the app image in debug mode but it doesn't log any errors when this message pops up, nor does it say anything when I swap the directory to something else.
I have 380GB free.

[Samueru-sama]

This looks like a problem with the application and not something I can fix here.

Asking AI I got this response:

Root cause: DiskSpaceHelper.GetPathRootForDiskSpaceCheck() in LibationFileManager/DiskSpaceHelper.cs uses Path.GetPathRoot(), which on Linux always returns / regardless of the actual mount point. It then queries DriveInfo("/") for free space.
On Bazzite (an immutable Fedora Kionite-based OS using ostree), / is a read-only deployment root with very limited free space. The user's actual data (home directories, /var) lives on a separate writable partition with 380GB free. So DriveInfo("/").AvailableFreeSpace returns near-zero, showing "0 MB free" in the preflight dialog and blocking downloads.
Relevant code:

• DiskSpaceHelper.cs:66-77 — GetPathRootForDiskSpaceCheck always resolves to / on Linux
• DiskSpaceHelper.cs:82-91 — TryGetAvailableFreeBytes queries DriveInfo(root) where root is always /
• DiskSpaceBackupPreflight.cs:31-33 — calls GetBackupDriveSpaces which triggers the check
• DiskFullUserMessage.cs — builds the "0 MB free" dialog
  The fix should be in GetPathRootForDiskSpaceCheck: on Linux, instead of using Path.GetPathRoot (which returns /), it should find the actual mount point of the path by enumerating DriveInfo.GetDrives() and matching the longest mount prefix that contains the path. This way free space would be correctly reported for the partition where the Books/InProgress directories actually reside.
  Workaround for the user: if Books and In Progress are set to directories under /var (e.g., /var/home/username/Libation), the fix should detect /var as the mount point and report correct free space.

[simmonsil]

Okay, I'll post the issue for the app itself and place your AI response message there if that sounds good.

[Samueru-sama]

sounds good