Hi folks (sway list CC'd as this also relevant for sway), in case you missed the thread on devel about systemd-oomd, the (imho) most important message for the i3 spin is below. If I understand this correctly, we'll have to ensure that systemd-oomd is disabled in the i3 spin, as it will simply kill the whole desktop if anything starts consuming too much memory. Unless anyone has an idea how to put every application that is launched from i3 into a cgroup in the same way that gnome shell already does that? The later would be of course preferable, as having apps in cgroups has a lot of advantages, but I don't know how feasible it is for us to achieve this. Cheers & happy holidays, Dan -------------------- Start of forwarded message -------------------- Date: Tue, 22 Dec 2020 13:03:14 -0600 From: Michael Catanzaro <mcatanzaro(a)gnome.org&gt; Subject: Re: Fedora 34 Change: Enable systemd-oomd by default for all variants (System-Wide Change) To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org&gt; On Tue, Dec 22, 2020 at 6:55 pm, Tom Seewald <tseewald(a)gmail.com&gt; wrote: If your desktop doesn't segregate apps and services into cgroups, systemd-oomd will kill the entire desktop whenever anything uses too much memory, because the desktop is going to be running in the same cgroup as the apps that it launches. So I think desktop spins (other than KDE) ought to opt out of this. It should be good for all Fedora editions, though (including Workstation, Server, Atomic, CoreOS), and also for KDE spin. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -------------------- End of forwarded message --------------------