Description of problem: After setting the APM level of my hard disk to 255 by means of gnome-disk-utility, the APM level is actually set to 255 as verifified by means of executing 'hdparm -B /dev/sda'. However, after suspend and resume, the APM level is set to 128 as verified by executing 'hdparm -B /dev/sda' again. Version-Release number of selected component (if applicable): storaged-2.6.2-1.fc25 How reproducible: Always. Steps to Reproduce: 1. Set APM level to 255. 2. Suspend and resume. 3. Run 'hdparm -B /dev/sda'. Actual results: The APM level is 128. Expected results: The APM level is 255. Additional info: - The hard disk is a Hitachi HTS723216L9SA60 installed in a Lenovo ThinkPad T400. - Moreover, after resume from suspend, gnome-disk-utility erroneously reports the target value 255 instead of the real value 128.
The same issue affects the precursor package udisks2-2.1.7-1.fc24 included in Fedora 24, see bug 1270838.
Issue reported upstream at https://github.com/storaged-project/storaged/issues/72.
I don't think Stef would be against me taking this one... Assigning to myself.
As mentioned in the freedesktop.org Bugzilla: storaged/udisks2 needs to re-read configuration and re-apply the settings after resume. I wonder what the API for detecting resumed system is nowadays: UPower is not emitting the "resume" signal and logind only sends signals about suspend/shutdown... Dropping script in /usr/lib/systemd/system-sleep/ doesn't seem right.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.