boven:/run/user # df -h | grep user
tmpfs 782M 24K 782M 1% /run/user/1000
boven:/run/user # mount | grep user
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=800312k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
boven:/run/user #
It looks as if this is used for temporary data that belongs to a user GUI session. I assume the desktop software creates it.
The idea is probably that it is easy to drop at logoff (by unmounting) and that, even when it keeps hanging until shutdown it will then certainly disapapear. It is also fast, which is nice when it is often used during a session.
A drawback is of course that memory is much more limited then mass-storage. And when several users are logged in it counts and counts. Thus I guess the limited size (800312k in my case above).
I assume that increasing it (will only work at login when the file system is created and mounted) must be done somewhere deep in the DE and or Display Manager or so.
Also the systems memory size will limit what is possible.
I never did what you do with Flatpak, but I am not sure that it should use that place for storing whatever they think they have to store temporary. :\
Hi
The tmpfs filesystem is ram based… a quick look at the man page indicates it should build in the directory run from, did you run the command flatpak build-init first?
Sets the size limit on the $XDG_RUNTIME_DIR runtime directory for each user who logs in. Takes a size in bytes, optionally suffixed with the usual K, G, M, and T suffixes, to the base 1024 (IEC). Alternatively, a numerical percentage suffixed by “%” may be specified, which sets the size limit relative to the amount of physical RAM. Defaults to 10%. Note that this size is a safety limit only. As each runtime directory is a tmpfs file system, it will only consume as much memory as is needed.