Package: systemd Version: 233-9 Severity: important Dear Maintainer,
I believe the bug #851492 should be reopened since there seems to be a regression after last upgrade and fix introduced in 232-11 doesn't work anymore. I've upgraded systemd (232-25 -> 233-9) and on next reboot my tmpfs on /tmp was 4K in size (which led for example to gdm3 not being able to display the greeter). I have 'Options=mode=1777,strictatime,size=70%' in /etc/systemd/system/tmp.mount Remount with: # mount -o remount,size=70% /tmp fixes the issue. (At least after previous remount to fixed size with # mount -o remount,size=4G /tmp) Also changing /etc/systemd/system/tmp.mount to fixed size=4G solves the issue after the reboot. Best regards, Jacek Politowski -- Package-specific info: -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.115 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.11.0-3 ii libaudit1 1:2.6.7-2 ii libblkid1 2.29.2-1 ii libc6 2.24-12 ii libcap2 1:2.25-1 ii libcryptsetup4 2:1.7.3-4 ii libgcrypt20 1.7.7-2 ii libgpg-error0 1.26-2 ii libidn11 1.33-1 ii libip4tc0 1.6.1-1 ii libkmod2 24-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.2+b1 ii libmount1 2.29.2-1 ii libpam0g 1.1.8-3.6 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b1 ii libsystemd0 233-9 ii mount 2.29.2-1 ii procps 2:3.3.12-3 ii util-linux 2.29.2-1 Versions of packages systemd recommends: ii dbus 1.10.18-1 ii libpam-systemd 233-9 Versions of packages systemd suggests: ii policykit-1 0.105-18 pn systemd-container <none> Versions of packages systemd is related to: pn dracut <none> ii initramfs-tools 0.130 ii udev 233-9 -- no debconf information
