Can I increase size of /run/user/1000 ?

Hi,

I am building Flatpak apps and it failed.

**error: **Failed to write file “/run/user/1000/.flatpak/595751139/info.0FT660”: write() failed: No space left on device

But my SSD have plenty of space left.

kev@localhost:~/Desktop/Software/Flatpak/com.github.buddhi1980.mandelbulber2> sudo df -h 
[sudo] password for root:  
Filesystem           Size  Used Avail Use% Mounted on 
devtmpfs             3.6G     0  3.6G   0% /dev 
tmpfs                3.6G     0  3.6G   0% /dev/shm 
tmpfs                1.5G  2.0M  1.5G   1% /run 
/dev/mapper/cr_root  477G  306G  169G  65% / 
tmpfs                3.6G     0  3.6G   0% /tmp 
/dev/mapper/cr_root  477G  306G  169G  65% /.snapshots 
/dev/mapper/cr_root  477G  306G  169G  65% /boot/grub2/i386-pc 
/dev/mapper/cr_root  477G  306G  169G  65% /boot/grub2/x86_64-efi 
/dev/mapper/cr_root  477G  306G  169G  65% /home 
/dev/mapper/cr_root  477G  306G  169G  65% /opt 
/dev/mapper/cr_root  477G  306G  169G  65% /srv 
/dev/mapper/cr_root  477G  306G  169G  65% /root 
/dev/mapper/cr_root  477G  306G  169G  65% /usr/local 
/dev/mapper/cr_root  477G  306G  169G  65% /var 
/dev/nvme0n1p1       511M  5.1M  506M   1% /boot/efi 
tmpfs                730M  730M     0 100% /run/user/1000


However, /run/user/1000 is 100% full and have only 730M of space.

My questions are how to increase this /run/user/1000 space and why is it was 730M in the first place.
Would this guide be correct? https://wiki.archlinux.org/title/Profile-sync-daemon#I_need_more_memory_to_accommodate_my_profile.2Fprofiles_in_.2Frun.2Fuser.2Fxxxx._How_can_I_allocate_more.3F

I use guide partition when installing openSUSE Tumbleweed, without swap partition. I create my own swapfile.

Hm, interesting. I have here

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 #

And the contents

boven:/run/user # l 1000/
ls: cannot access '1000/gvfs': Permission denied
total 4
drwx------ 9 henk wij  300 Jul 20 15:16 ./
drwxr-xr-x 3 root root  60 Jul 20 15:15 ../
-rw-r--r-- 1 henk wij   69 Jul 20 12:14 KSMserver__0
drwxr-xr-x 2 henk wij  120 Jul 20 12:14 akonadi/
srw-rw-rw- 1 henk wij    0 Jul 20 12:14 bus=
drwx------ 3 henk wij   60 Jul 20 12:14 dbus-1/
drwx------ 2 henk wij   60 Jul 20 12:14 dconf/
drwx------ 2 henk wij  120 Jul 20 12:14 gnupg/
d????????? ? ?    ?      ?            ? gvfs/
srw------- 1 henk wij    0 Jul 20 12:14 kdeinit5__0=
srwxr-xr-x 1 henk wij    0 Jul 20 12:16 kio_http_cache_cleaner=
srwxr-xr-x 1 henk wij    0 Jul 20 12:14 klauncherwKmNOL.1.slave-socket=
srw-rw-rw- 1 henk wij    0 Jul 20 12:14 pipewire-0=
drwx------ 2 henk wij   80 Jul 20 12:14 pulse/
drwxr-xr-x 3 henk wij  100 Jul 20 12:14 systemd/
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?

Hi,

I use the command

flatpak-builder --install --force-clean --user build com.github.buddhi1980.mandelbulber2.yaml

which will create build directory and build it there.

Anyway, I follow the guide Profile-sync-daemon - ArchWiki
And I use 30% for RuntimeDirectorySize and I have 2.2GiB for run/user/1000 now.

kev@localhost:~> sudo df -h 
Filesystem           Size  Used Avail Use% Mounted on 
devtmpfs             3.6G     0  3.6G   0% /dev 
tmpfs                3.6G     0  3.6G   0% /dev/shm 
tmpfs                1.5G  2.0M  1.5G   1% /run 
/dev/mapper/cr_root  477G  306G  169G  65% / 
/dev/mapper/cr_root  477G  306G  169G  65% /.snapshots 
/dev/mapper/cr_root  477G  306G  169G  65% /boot/grub2/i386-pc 
/dev/mapper/cr_root  477G  306G  169G  65% /boot/grub2/x86_64-efi 
/dev/mapper/cr_root  477G  306G  169G  65% /home 
/dev/mapper/cr_root  477G  306G  169G  65% /opt 
/dev/mapper/cr_root  477G  306G  169G  65% /srv 
/dev/mapper/cr_root  477G  306G  169G  65% /root 
/dev/mapper/cr_root  477G  306G  169G  65% /usr/local 
/dev/mapper/cr_root  477G  306G  169G  65% /var 
tmpfs                3.6G     0  3.6G   0% /tmp 
/dev/nvme0n1p1       511M  5.1M  506M   1% /boot/efi 
tmpfs                2.2G  245M  1.9G  12% /run/user/1000



Thanks.

Hi
Have you not tried my rpm?

@malcolmlewis
Yes, I have tried it, but I’m moving most of my package to Flatpak now.

From man logind.conf:

RuntimeDirectorySize=

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.

Add the above to /etc/systemd/logind.conf.