Does this package conflict with systemd oom?

Bug #1974268 reported by Tim Richardson
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Default settings and artwork for Baltix OS
Mantas Kriaučiūnas
earlyoom (Ubuntu)

Bug Description

Ubuntu now defaults to systemd oom handling.
Is there a way to warn an upgrade user who has earlyoom installed that the two are in conflict (assuming that they are).

Tags: jammy
Chris Guiver (guiverc)
tags: added: jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in earlyoom (Ubuntu):
status: New → Confirmed
Changed in baltix-default-settings:
assignee: nobody → Mantas Kriaučiūnas (mantas)
Revision history for this message
Yangfl (mmyangfl) wrote :

Yeah, not sure about this. Having multiple oom handlers is strange, but can still work.

A warning would be enough. Is there a way to have systemd warn about it but not prevent it?

Changed in baltix-default-settings:
status: New → Incomplete
status: Incomplete → New
Changed in earlyoom (Ubuntu):
status: Confirmed → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.