systemd: session-6.scope: Deactivated successfully. systemd: session-6.scope: systemd-oomd killed 82 process(es) in this unit. at-spi2-registryd: X connection to :0 broken (explicit kill or server shutdown). polkitd: Unregistered Authentication Agent for unix-session:6 (system bus name :1.139, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected from bus) XFCE, LXQT, MATE-Compiz, Cinnamon, LXDE, SOAS (wtf is that) and i3 (new for f34) should be tested/covered first. `sway` is certainly affected, but I assume that official desktop spins, i. So while I agree that cgroups are the proper way forward to handle OOMs, I'm not sure that we're ready for that for workstation usage. For me it looked like a `sway` bug (segfault or something) until I looked into `journalctl`, but I suppose that average cinnamon/mate/xfce/ user will not look into `journalctl` and just think `Oh well, fedora is just crashing sometimes`. The session is killed without any notification pre/post kill. I understand that having two userspace oom-killers is not ideal and having default/unified system services on more setups is desired (I was planning to switch to systemd-oomd), but silently disabling manually installed/configured OOM handler is not good.Ģ. While I knew that systemd-oomd would be enabled in f34, it was unexpected to have earlyoom (potentially with it's own non-default settings) replaced by it. I already configured memory-killers as they were before, butġ. Some memory-hungry processes like browser is killed and session with WM still runs. Three times already and I don't see any other systemd-oomd actions (`earlyoom` killed firefox cnontent processes previously and I saw it), so I suppose always?
Version-Release number of selected component (if applicable): Oomd kills the whole session instead of being more selective, which is not very handy for a laptop with the single purpose of running user session. Waiting for processes to exit.įeb 28 19:57:37 ojab-notebook systemd: session-1.scope: systemd-oomd killed 514 process(es) in this unit.įeb 28 19:57:37 ojab-notebook systemd: getty: Deactivated successfully. I'm running my WM via `exec env $(systemctl -user show-environment) dbus-run-session - sway` in console without any display manager andįeb 28 19:57:37 ojab-notebook systemd-oomd: Swap used (7432306688) / total (8229220352) is more than 90.00%įeb 28 19:57:37 ojab-notebook systemd-logind: Session 1 logged out.
0 kommentar(er)
