Hide Forgot
Description of problem: I would like to have a choice (GUI setting) to select system behavior of lid switch depending on power state (AC/battery). Version-Release number of selected component (if applicable): any recent How reproducible: 100% Steps to Reproduce: 1. close lid when ac adapter connected 2. either suspend or ignore 3. close lid when ad acapter not connected (battery fed) 4. same behavior as in 2. (no chance to set different behavior) Actual results: Not possible to have different behavior upon lid switch activation depending on power source (ac/battery) Expected results: End-user should be able to customize this setting (e.g in gnome-control-center or gnome-tweak-tool or ...) Additional info:
For some background: https://ask.fedoraproject.org/en/question/86649/power-management-policy-gnome-318/ The problem comes down to a few things (some of which are due to hardware support issues, but not all): on AC: 1)I have long running tasks but I don't want to leave the laptop open (there are several reasons for this, but, let's just consider the Pet Problem) 2)my computer doesn't resume reliably (this can be dealt with by either editing a gsettings, um, setting, or editing logind.conf, BUT this seems as though it should be something that would be exposed more naturally in the gui under Settings->Power->Suspend/PowerOff) on battery: 1)even though my computer resumes unreliably I'm willing to trade reliability for the possibility of actually using it----after all, I can always reboot (and I use btrfs which recovers really well from unexpected shutdowns) 2)in my particular case, resuming from S4 isn't far less reliable than S3, so, related to the above, assuming suspension works, I'd rather have the possibility of my system saving state through hybrid-suspend, than losing everything I hope this makes it clear why this would make our systems more reliable.
ping?
Um, ping?
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.
Nice triage folks!