The journal snippet is brief, so I can't see what started the killing spree. Generally it seems like oomd is doing the right thing, and if you want to have more control over what gets killed, you could add drop-in confings to avoid or omit certain things.
E.g., if you wanted to avoid dbus.service getting killed, then you would do: $ mkdir -p /etc/systemd/system/dbus.service.d/ $ cat > /etc/systemd/system/dbus.service.d/oomd-avoid.conf << EOF [Service] ManagedOOMPreference=avoid EOF $ systemctl daemon-reload See https://www.freedesktop.org/software/systemd/man/latest/systemd.resource- control.html#ManagedOOMPreference=none%7Cavoid%7Comit for more information. For now, I would try adding some drop-ins (look at your own logs to see what units should get this treatment) as a workaround. But, it's definitely worth investigating the application that is apparently consistently causing high memory pressure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075104 Title: user session is randomly terminated by systemd-oom when the system is left alone for a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
