I just ran the `Dotfiles persistence` scenario (the only potentially relevant bit from that is that activating persistence could be related) on my system and it failed while logging in due to `dbus.service` being OOM reaped: ``` Oct 24 09:55:37 amnesia systemd-oomd[894]: Considered 40 cgroups for killing, top candidates were: Oct 24 09:55:37 amnesia systemd-oomd[894]: Path: /user.slice/user-1000.slice/user@1000.service/session.slice/dbus.service Oct 24 09:55:37 amnesia systemd-oomd[894]: Memory Pressure Limit: 0.00% Oct 24 09:55:37 amnesia systemd-oomd[894]: Pressure: Avg10: 20.61 Avg60: 5.29 Avg300: 1.18 Total: 3s Oct 24 09:55:37 amnesia systemd-oomd[894]: Current Memory Usage: 141.4M Oct 24 09:55:37 amnesia systemd-oomd[894]: Memory Min: 0B Oct 24 09:55:37 amnesia systemd-oomd[894]: Memory Low: 0B Oct 24 09:55:37 amnesia systemd-oomd[894]: Pgscan: 3482 Oct 24 09:55:37 amnesia systemd-oomd[894]: Last Pgscan: 1244 [...] Oct 24 09:55:37 amnesia systemd[8024]: dbus.service: systemd-oomd killed 23 process(es) in this unit. Oct 24 09:55:37 amnesia systemd[8024]: dbus.service: Main process exited, code=killed, status=9/KILL ``` The result is that we get stuck in the GDM session (but the Welcome Screen exits without issue). [Full journal](/uploads/e2f80e7e88c715897bb7849c37477555/journal)