Thank you for testing.
That's expected as we're only acting on configuration file changes during early boot. This allows us to resize swap files before any swap usage occurs (i.e. on some systems a swapoff/resize/swapon might be a disruptive operation)it needed a reboot before the zram-based swap showed up.
Your journalctl is showing a timeout failure for the dev-zram0.device. Is this a one-off that self-corrects or is it a persistent problem?journalctl:
...Code:
Aug 19 14:50:41 trixie32 systemd[1]: dev-zram0.device: Job dev-zram0.device/start failed with result 'timeout'.
Statistics: Posted by roliver — Tue Aug 19, 2025 2:40 pm