I just got the phone today, put in my 128Gb memory expansion card and SIM card, then due to the various posts in this forum recommending the elagost Signal flatpak here:
https://elagost.com/flatpak/
I went ahead with trying the install. The page reads:
[Stuff redacted] Warning: While pulling runtime/org.freedesktop.Platform.GL.default/aarch64/22.08 from remote flathub: Delta requires 346.2 MB free space, but only 253.5 MB available
Warning: While pulling runtime/org.freedesktop.Platform.GL.default/aarch64/22.08-extra from remote flathub: Delta requires 346.2 MB free space, but only 253.5 MB available
Warning: Not enough disk space to complete this operation
Warning: Not enough disk space to complete this operation
Error: While pulling runtime/org.freedesktop.Platform/aarch64/22.08 from remote flathub: Delta requires 488.2 MB free space, but only 252.9 MB available
error: Failed to install org.freedesktop.Platform: While pulling runtime/org.freedesktop.Platform/aarch64/22.08 from remote flathub: Delta requires 488.2 MB free space, but only 252.9 MB available
The filesystem is shockingly full in the bits I need it not to be:
I had the same problem last week and solved it by doing :
$ df -kh /
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/disk/by-uuid/xxxx 3,6G 3,4G 79M 98% /
$ sudo resize2fs /dev/mapper/crypt_root
resize2fs 1.46.2 (28-Feb-2021)
Filesystem at /dev/mapper/crypt_root is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 4
The filesystem on /dev/mapper/crypt_root is now 7509504 (4k) blocks long.
$ df -kh /
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/disk/by-uuid/xxx 29G 3,4G 24G 13% /
$
I also had the issue with the 3.something GiB root filesystem with a new device (no reflashing or anything), and I was also able to fix it with @marcf’s suggestion. Thanks!
The background of this topic is … when you download a Librem 5 disk image, the disk image is roughly 5 GB in size i.e. big enough to contain everything it needs to contain in order to boot and run normally but not the full size of the actual eMMC drive. If a disk image were full size then it would take proportionately longer to transfer it via USB during flashing and proportionately longer to write it to the eMMC drive - and it would occupy more disk space on the host computer.
In the early days, you had to expand the file system manually after flashing (from roughly 5 GB to roughly 30 GB). Reportedly that happens automatically now (although it didn’t happen for me when I reflashed late last year).
In any case, the symptom is that / is nearly full because / is only roughly 5 GB and that clearly doesn’t apply to your phone.
Please post output from
journalctl --disk-usage
(I am punting that /var is bloated because you never cleaned your journal.)
Difficult to say what is filling ~purism so you will have to drill deeper. Browser disk cache? Flatpaks?
Thank you so much for your answer, Irvinewade!!
I apologise for my post in the wrong topic
I didn’t understand it! It’s clear, now, the topic after your explanation!!
Then I used ChatGPT to explain me in an easy way how to see the weight of epiphany and flatpak as you suggested and how to clean it! What do you think about it? I attached screenshots!
Thank you again for your help and apologise for the wrong topic! If you desire you could move my posts in the right topic or you could explain me how to do that!
You will need help from someone other than me in order to tame your flatpaks.
You may not have identified all the usage in /var given that you originally posted that it contained 14GB and /var/lib/flatpak accounts for 9.2GB of it.
You need to keep searching for what in ~purism is tying up a lot of disk space.