Description of problem: systemd-oomd keeps killing processes even when I have lots of swap space. I have tried to create an override file 99-oomd-override.conf according to an old Fedora bug report on systemd-oomd, but the override doesn't seem to work. Version-Release number of selected component (if applicable): unsure How reproducible: Intermittent. systemd-oomd mainly kills Firefox, at least a couple of times a day. It has even killed gnome terminal when I was running $sudo dnf update -y, so now I am circumventing that issue by bring up a real terminal <ctrl>+<alt>+<F3>. Steps to Reproduce: 1. Running Firefox 2. 3. Actual results: Firefox gets killed at some random interval. Expected results: Firefox keeps running. If no immediate solution is available it would be nice to have some way to override the default setting in the meantime. Additional info: Here is my swap listing: [ruppie@fedora system]$ swapon -s Filename Type Size Used Priority /dev/zram0 partition 8049660 476928 100 /dev/sda5 partition 51199996 0 -2
'rpm -q systemd-oomd-defaults' ? We removed oomd configuration to monitor swap use in systemd-251.4-38.fc37. Do you maybe have some left-over configuration that messes this up? Please attach a log ('journalctl -b') from a boot where the issue reproduces. We might be able to say more with that.
Created attachment 1950034 [details] output of journalctl -b Output of journalctl -b after Firefox crashed today. It's pretty big.
Output of "rpm -q systemd-oomd-defaults" is: rpm -q systemd-oomd-defaults Please note that my system started as Fedora 34 and was upgraded several times to Fedora 37.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.