[Ubuntu 18.04] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Invalid
|
High
|
rahmadani | ||
pm-utils (Ubuntu) |
Invalid
|
High
|
rahmadani |
Bug Description
== Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
systemd and pm-utils interprets CanSuspend states differently and reports it as supported or not in a conflicting way.
# gdbus call --system --dest org.freedesktop
('yes',)
# pm-is-supported --suspend
# echo $?
1
Both systemd and pm-is-supported looks into /sys/power/state file to check if suspend is supported.
pm-is-supported --suspend returns true if either "standby" or "mem" is present in the file.
( /usr/lib/
systemd(
( https:/
# cat /sys/power/state
freeze
So here, pm-is-supported --suspend returns false and gdbus returns true.
Both these utilities interpret /sys/power/state differently.
Secondly, systemd should split CanSuspend to Cansuspend+
Impact of this inconsistency can be felt from Libvirt supported pm states:
To reduce ABI dependency, libvirt queries the available states via dbus, if not falls to pm-utils. Libvirt won't check for strings in sys/power/state and interpret directly.
so due to this, libvirt will list that suspend_to_mem is supported from virsh capabilities but ideally it might not.
tags: | added: architecture-ppc64le bugnameltc-156093 severity-high targetmilestone-inin1710 |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → pm-utils (Ubuntu) |
tags: | added: artful |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
Changed in pm-utils (Ubuntu): | |
milestone: | none → ubuntu-17.10 |
importance: | Undecided → High |
tags: | added: triage-g |
Changed in ubuntu-power-systems: | |
status: | New → Incomplete |
Changed in pm-utils (Ubuntu): | |
status: | New → Incomplete |
Changed in pm-utils (Ubuntu): | |
milestone: | ubuntu-17.10 → ubuntu-18.04 |
Changed in pm-utils (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in ubuntu-power-systems: | |
status: | Incomplete → Invalid |
Changed in pm-utils (Ubuntu): | |
assignee: | nobody → rahmadani (rahmadani) |
Changed in ubuntu-power-systems: | |
assignee: | nobody → rahmadani (rahmadani) |
This package / The package is part of the universe section of the Ubuntu archive. Universe packages are maintained by the community, and the maintainers do not necessarily work for Canonical, therefore these packages are not always supported directly by Canonical. /www.debian. org/Bugs/ Reporting use this link to report your issue and submit a fix. /wiki.ubuntu. com/Debian/ Bugs will provide you an overview on how to handle bugs that are reported to Debian and subsequently to Ubuntu.
The existing process to update packages in the Universe archive with patches, is as follows:
1. Upstream: Upstream your fix to the appropriate upstream project.
2. Debian: once your patch is ack’ed and accepted upstream, you need to request a merge of this patch to the package in Debian stable. https:/
3. Ubuntu: Once it is merged into Debian stable, request a merge of this package with Ubuntu. https:/
- The merge request lands by default in Ubuntu's current development release (today ‘Artful’).
- If required an SRU may follow to get the changes into already released Ubuntu versions (like ‘Xenial’ or ‘Zesty’).
Work with the respective upstream maintainers (Debian and Ubuntu) is required during this process. For critical issues we can advise you as you go through this process and help push the patches through by chasing the appropriate project contributors.
[To find out if a package is a universe package use: apt policy <package-name>.]