Note: update needs to installed with "dnf update mate-desktop* --best --allowerasing" Which will be remove systemd-oomd-defaults.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2022-8d14f0b9ecPlease login to add feedback.
This update has been submitted for testing by raveit65.
This update's test gating status has been changed to 'ignored'.
This update has been submitted for testing by raveit65.
This update has been pushed to testing.
I don't have either earlyoom or systemd-oomd installed and this update forces earlyoom on me. I've never experienced any out of memory issues on my machines or had my desktop sessions killed, even on those with 8GB or less. Please drop the earlyoom or mate-desktop-systemd requirement or at least change to a weak dependency.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
FWIW, nothing requires systemd-oomd-defaults, not even weakly, so it can be uninstalled with no dependency issues.
No, this isn't true. I've tested this several times and since f34 systemd-oomd-defaults is installed as default. Please read https://fedoraproject.org/wiki/Changes/EnableSystemdOomd and https://bugzilla.redhat.com/show_bug.cgi?id=1933494 Removing systemd-oomd-defaults will disable systemd-oomd.service. So, Conflicts: systemd-oomd-defaults is needed to remove systemd-oomd-defaults from existing installations, otherwise 2 oom memory services are enabled. And sorry, that you never experience memory problems isn't the point. Here is a user who reported the problem. systemd-oomd kills the whole mate session because of missing cgroups support. https://bugzilla.redhat.com/show_bug.cgi?id=2068699 Please revert your negative karma.
And if you not trust me and all the people from reports. Revert this update, install systemd-oomd-defaults, and try again to install the update :)
You are missing my point. I can uninstall
systemd-oomd-defaults, but I can't uninstallearlyoomafter installing this update. It makes things worse for me, hence the negative karma.You can't do
systemctl disable earlyoomif you don't like it?Do you give positive karma when is use
Recommends: earlyoom?error......is use = i use
I can live with
Recommends: earlyoominstead ofRequires:. I'd change my vote here in that case. I'm not sure why you thought you needed to create a new subpackage just for fixing #2068699. You could have added theConflicts: systemd-oomd-defaultsandRecommends: earlyoomto the-configssubpackage. Each new subpackage increases the amount of repo metadata that dnf has to process. Please revert creation of the-systemdsubpackage and fold it back into-configs.raveit65 edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by raveit65.
raveit65 edited this update.
I am so happy to spend a lot of my spare time to make you happy.
PS: Why you're highlighting nearly every word in a short post? This looks very unfriendly and aggressive......
LGTM
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Testing new F36 respin here, and at first update test I have this output:
sigh, please follow links and read......
Thanks, I readed all of them. So the problem is that when building the new MATE respin we used systemd-oomd-defaults instead of earlyoom. OK must rebuild that right. Once again thanks for the attention @raveit65
Still wondering why you are not using fedora-kickstart for respin? I did all for f34 https://pagure.io/fedora-kickstarts/c/022f04580e1261dd8bfb13c9d9173d65eddd5c45?branch=f34 f35 https://pagure.io/fedora-kickstarts/c/3cfe995016eebde3204dab81b30d9768aab0df17?branch=f35 f36 https://pagure.io/fedora-kickstarts/c/8d939b753ce540a3b5f0edb087e60769907b12ad?branch=f36 and main https://pagure.io/fedora-kickstarts/c/f1ae8a572294879ff93370f3950754218013a5c1?branch=main