Description of problem: Hibernate is not working on Fedora 23. What happens is that the system does turn off a few seconds after being hibernated, but then it won't resume when the computer is turned on again. The saved state is lost, unsaved data is lost, just as if the system had crashed. If hibernation is not possible or broken, the user should be warned and the system should not go into a state from which it cannot recover (resume). As it is now, no error message is shown and the system shuts down, losing its state, so the user loses their work. Version-Release number of selected component (if applicable): Fedora 23. How reproducible: Not sure. Steps to Reproduce: 1. Use Cinnamon (for example). 2. In the Cinnamon menu, select "Quit", then "Hibernate". 3. The system goes off, probably trying to hibernate even though it does not work. Actual results: System tries to hibernate and does not show an error message if it doesn't work. When the computer is turned on again, Fedora boots normally instead of resuming the state. All unsaved data is lost. Expected results: If the hibernate feature is broken for some reason - or maybe if user interaction by an experienced admin is required - it should show an error message *instead* of trying to hibernate without success and losing its state. Additional info: A modern operating system that can't hibernate is one thing. An operating system that pretends or tries to hibernate without checking if it's even possible or if it worked, losing its state, is twice as bad.
Does this command work? systemctl hibernate
No: $ systemctl hibernate Failed to hibernate system via logind: Sleep verb not supported Again, the main point of this bug is that the system should not even allow the user to suspend (= crash since state will be lost) if it's broken on Fedora. Don't show features that don't work and cause data loss.
(In reply to Basic Six from comment #2) > Again, the main point of this bug is that the system should not even allow > the user to suspend (= crash since state will be lost) if it's broken on > Fedora. Don't show features that don't work and cause data loss. It's not the DE's responsibility to test to see if systemd/logind can hibernate properly. In fact I don't think it's even systemd/logind responsibility to check the system can hibernate properly. It's your responsibility to check at not use it if your system can't handle it !
Maybe it's not the DE's responsibility, not sure. But I don't agree with the claim that it should be the user's responsibility to check if Fedora is able to hibernate without losing data (btw. how - by hibernating, which would lead to such a "crash"?). From a user's perspective, if hibernating the system does not work and leads to data loss, it's a bug. Maybe, the system could show an error message like "hibernation not possible (because config xyz missing)"?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
After upgrading to Fedora 24, Cinnamon did not show a "Hibernate" option anymore. This solves the main problem why this bug was opened - the option to let the user crash the system (unintentionally) is now disabled. After following the official instructions ("Common F24 bugs", "Hibernation doesn't work from a standard install") to edit the Grub configuration, the "Hibernate" button is enabled and it actually works. It's unfortunate that hibernation is not possible by default and that most users (who are not familiar with the command line and should not touch config files) are not able to enable it themselves, but that's off-topic and will hopefully be fixed soon. However, before editing the Grub configuration, the system still tried to hibernate automatically when the battery was low. It showed a popup notification that the system was about to hibernate.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.