Comment 4 for bug 1706948

I'm not sure that Frank's follow-up comment and package assignment corresponds to the original bug report.

If I understand the original bug report correctly, the problem is that systemd reports 'yes' to CanSuspend on systems that only support 'freeze', and that this is seen as incorrect.

Therefore the problem is not inconsistency between systemd and pm-utils; the problem is inconsistency between systemd and the consumer of the CanSuspend API (in this case, libvirt).

This API is org.freedesktop.login1.Manager.CanSuspend, which is part of logind, which is defined by systemd. So unless this is a behavior change in systemd, it doesn't appear to be a bug that we can do anything about directly in Ubuntu; the semantics of this API are defined by upstream, and any changes to those semantics would need to be negotiated with upstream.

For my part, I am not clear why 'freeze' should not be considered a subcategory of suspend-to-mem, so perhaps this bug will be 'wontfix' by systemd upstream. At the very least, this bug report seems to be missing an explanation of why the current behavior of systemd is wrong.

In any case, it's clear to me that no change in pm-utils will address the root problem being reported, because a) libvirt prefers logind over pm-utils, we always have logind present in 18.04, and we do not install pm-utils by default, so changing pm-utils will not change the observed behavior; and b) AIUI the bug submitter is asserting that pm-utils' behavior is the correct behavior.