Description of problem: I need to know when the machine has just been resumed from a suspended state. All other distributions seem to support the standard dbus "Resuming" signal on "/org/freedesktop/UPower", but on Fedora 20 x86_64 nothing happens. Version-Release number of selected component (if applicable): dbus-1.6.12-8.fc20.x86_64 upower-0.9.23-2.fc20.x86_64 How reproducible: 100%. Every time. No matter what tool I use to try to get the notification, nothing happens. Steps to Reproduce: 1. Start a dbus monitor or other dbus application and wait for "Resuming" signal 2. Suspend then resume the machine. Actual results: Nothing happens, no events fire. Expected results: The "Resuming" signal should fire. Additional info: Instead of using dbus-monitor, you can also test using python dbus scripts, here are two examples: http://serverfault.com/questions/191381/what-dbus-signal-is-sent-on-system-suspend/210687#210687 http://askubuntu.com/questions/183516/how-do-i-detect-when-my-system-wakes-up-from-suspend-via-dbus-or-similar-in-a-py Otherwise, dbus-monitor should also give you the desired signal: dbus-monitor --system "type='signal',interface='org.freedesktop.UPower'" There is a systemd upower service file which looks like it should send the signal when instructed to do so: #/usr/lib/systemd/system/upower.service: dbus-send --system --type=signal --dest=org.freedesktop.UPower \ /org/freedesktop/UPower org.freedesktop.UPower.Resuming But again, launching it manually does nothing either: no signals are received by any of the test applications.
I believe that's part of the api that was deprecated in recent upower releases (and the version included in fedora 20), and applications are expected to use the (systemd) org.freedesktop.login1 interfaces now.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.