Description of problem: mate-desktop-1.26.0-3.fc36 will be install 80-mate-compiz.preset https://src.fedoraproject.org/rpms/mate-desktop/blob/rawhide/f/80-mate-compiz.preset which enable earlyoom.service if installed. The f36 mate-compiz spin install earlyoom and blacklist systemd-oomd-defaults. See https://pagure.io/fedora-kickstarts/c/f1ae8a572294879ff93370f3950754218013a5c1?branch=main In result without 80-mate-compiz.preset earlyoom will be installed but not enabled. So a freeze exception is needed to avoid a installation from spin without a out-of-memory (OOM) function. This update will fix the issue. https://bodhi.fedoraproject.org/updates/FEDORA-2022-825c6992fa And original problem with systemd-oomd-defaults was posted here https://bugzilla.redhat.com/show_bug.cgi?id=2068699 Sorry, i missed the very short time between beta release and release release freeze. I think this time is to short for a single person like me to update the Mate Spin for a new release. But that's another story.
Proposed as a Freeze Exception for 36-final by Fedora user raveit65 using the blocker tracking app because: Freeze exception is needed to avoid a installation from spin without a out-of-memory (OOM) function. See bug details.
FEDORA-2022-825c6992fa has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-825c6992fa
Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/728 The decision to classify this bug as an AcceptedFreezeException was made: "The Mate Spin would be released with earlyoom disabled without pulling this in which isn't desired state as per Mate maintainer."
FEDORA-2022-825c6992fa has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
The issue has been fixed by an update mentioned above.