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. 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://www.debian.org/Bugs/Reporting use this link to report your issue and submit a fix. 3. Ubuntu: Once it is merged into Debian stable, request a merge of this package with Ubuntu. https://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 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>.]
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1706948 Title: [Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils Status in The Ubuntu-power-systems project: New Status in pm-utils package in Ubuntu: New 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.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend ('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/pm-utils/pm-functions ) systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is present in the file. ( https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c ) # 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+CanFreeze Or don't report freeze as 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
