(no title)

Published (click to see context) on 08/07/2022 by Morgan Bazalgette • 2 minutes
Okay, it's bitching about Linux Desktop o'clock again.
I use a pretty standard Ubuntu installation, with no fancy things as I got a real life and a job and have no time to configure Arch/Gentoo/$neckbeard_distro to do what I want it to.
Why, then, is the default userspace OOM killer, which is installed by default on ubuntu, not capable of signaling to the user that a) a oom kill is about to happen and most importantly that b) a oom kill has happened?
why is it not configured by default to avoid killing some very important processes on a desktop environment, like dbus?
why is it not configured by default to attempt killing processes with SIGTERM instead of SIGKILL, and only use SIGKILL when the situation gets really serious?

after a few minutes of digging, I found nohang which seems to do what I need:
but it's still absurd to me that even though there are companies that have some kind of commitment to providing a decent linux desktop experience, this is an issue that has not been tackled while I certainly am not the only one this has happened to.
I'd really not want to resort to some unmaintained small project which literally has in its README "Known problems: the documentation is terrible".
And all of this really saddens me, because even though we're seeing enormous leap forwards on some areas, including videogames where it's getting so good that many windows-only games now run even better than windows on the steamdeck, there are still some basic things like this one where if I were not a technical user I'd have a hell of a time figuring out what the hell is going on and how to solve the problem (I mean, there's really no way you can install nohang, enable it and disable systemd-oomd without technical knowledge)