Correct, you don’t need the one with the dot.
But ‘active’ isn’t a directory, it’s a link pointing to the non-dot prefixed dir (I had only one).
My folder currently contains:
9189a0c9b3c5495ad643b79bdd1b941df088ab3edc629172d4210b33d02c405a
active -> 9189a0c9b3c5495ad643b79bdd1b941df088ab3edc629172d4210b33d02c405a
.timestamp
It works … but I don’t take any responsibilities 
Okay. Thanks.
No complaints yet about the new leaner one. I’ll wait a bit before I delete anything.
Where exaclty is Flatpak in the /home directory?
And where is that generaljournal cache at?
I think he means
~/.local/share/flatpak
Try
sudo journalctl --vacuum-time=10d
it’s been explained above, on this thread
Ah, okay. Thanks.
Just checking whether it was the same journal cleaning instruction I had seen before, or another one. It’s the same.
And the cache in the flatpak dir is empty.
Hello:
To follow up on this:
Can somebody please help us poor souls who have Librem 5 and want to install Flatpaks without unecessary bloat? I realize Purism has other things to do, but this is a silly issue.
Doing things on my own, again, I took a whim and used this command:
rm -r /var/lib/flatpak/appstream/flathub/aarch64
That deleted the whole directory and files in it. I got rid of about 2 GB of what appear to be unnecessary bloat.
Warning, I am a novice and I guarantee nothing! Run that command at your own risk.
I hope that helps someone. There have been no adverse effects on my us of Flatpak apps on the phone - yet.
I just reflash the latest Evergreen LUKS and DAS U-Boot images to deal with bloat or misconfigurations. Far more often I do it due to the latter than the former, since I hardly install anything to begin with.
Ok. Thank you. Can you make it easy on me and tell me how to easily do that?
The following official documentation may get you pointed in the right direction: https://docs.puri.sm/Librem_5/Troubleshooting/Reflashing.html
Here is a high-level overview:
Download, verify, and install the PureOS 10.3 image on a USB drive using disk-writing software such as balenaEtcher.
Boot into the PureOS USB live image.
Follow the instructions listed by Irvine Wade above this post, or alternatively this one below.
git first before mirroring the repository. Also note the command sudo apt build-dep .
You just saved me 1.6 GB of space. Merci beaucoup!
I took the risk and did:
sudo rm -rf /var/lib/flatpak/appstream
This resulted in 4.3GB of extra storage. I did not notice any negative side effects, but use at own risk.
The growing /var/lib/flatpak/appstream is a bug that is fixed in a newer flatpak release.
Doing a sudo rm -r .* in var/lib/flatpak/appstream/flathub/aarch64 works too, and it is somewhat less drastic.
Well done! Bought me three to four times more than vacuum.
I have just found out that, to clean up unused files and prevent Flatpak’s footprint from filling up all available space, I need to run regularly something along the following lines.
$ flatpak update
$ flatpak remove --unused --delete-data
$ rm -r ~/.local/share/flatpak/appstream/*
$ sudo rm -r /var/lib/flatpak/appstream/*
$ sudo flatpak repair
$ flatpak --user repair
As far as I understand, It is necessary to delete the contents of appstream directories mannually due to a bug in the Byzantium version of Flatpak, which was fixed upstream. So, it is hopefully not required on Crimson.
Running “repair” is necessary to prune unused binaries in the objects store. I assume that Flatpak has a legitimate reason to keep those files. So, “repair” needs to be run regularly to remove them. But are the relatively unsophisticated users of Librem 5 supposed to know about that? Shouldn’t the PureOS distribution take out the trash for them? What am I missing?
Probably, yes, but it doesn’t as such know what flatpak even does - so perhaps installing flatpak should provide that automatic cleanup.
If it were me who installed the flatpak package on a 31 GB partition, I probably wouldn’t suggest that PureOS should take care of that. However, this is something I would expect Debian to take care of. And it comes pre-installed. Several librem5-* and pureos-* metapackages directly or indirectly depend on it. Flatpak runs on different systems and has various applications. I assume that there may be a valid reason to do not prune the object store for something and keep them for history. Of course, the Purism team could probably work with upstream to convince them, or modify the local version, but it would be unnessary if it is possible to include appropriate maintenance scripts in one of those librem5-* or pureos-* packages that are not metapackages.
It is still installed and it should still take care of its own cleanup.
If there’s a good reason not to clean up in some circumstances, it should still give the user configuration options that would nevertheless clean up.
Maybe their design assumption is that everyone has an approx. 256GB disk (or larger), so cleanup is not a priority.
