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): udisks2-2.1.6-1.fc23 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.
It seems that udisk2 needs to provide systemd support with a script in /usr/lib/systemd/system-sleep/ similar to the following which resets the APM level to 254 after resume from suspend: -- #!/bin/sh [ "$1" = "post" ] && exec /usr/sbin/hdparm -B 254 /dev/sda exit 0 --
This issue affects Fedora 23 but likewise Fedora 24 including package udisks2-2.1.7-1.fc24.
Do you have a freedesktop Bugzilla account? This would be good to report upstream. Ideally you would do that, so you stay CCed on the issue, but I can forward it if you prefer.
udisks is retired. Reassigning to storaged maintainers to assess whether the bug might affect storaged.
Fedora 24 is using udisks2 by default unlike Fedora 25 which is why I have reported the present issue a second time for storaged and Fedora 25 (storaged just behaves the same): bug 1270838 for udisks2 and Fedora 24 and bug 1357190 for storaged and Fedora 25. What is needed for Fedora 24 is a new build of the existing package storaged which obsoletes udisks2; only then it is justified to set the component from udisks2 to storaged.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
There's been some discussion about this upstream: I have even created some workaround in storaged to re-set the APM level on resume. However storaged/udisks2 is a D-Bus activated service and nothing guarantees it would be running at the time tha APM level needs to be set (e.g., on boot).
(In reply to Tomas Smetana from comment #7) According to my comment from 2016-07-22 at https://github.com/storaged-project/storaged/issues/72, the test build storaged-2.6.2-2.6.fc23 does restore the correct APM level after resume from suspend. However, there was an issue regarding the precise moment when drive settings got applied.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
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.