Created attachment 1362328 [details] Console output using --no-daemon --debug flags Description of problem: Whenever I close the laptop lid, the options in the power manager are ignored. It doesn't matter if I set it to lock screen, suspend, hibernate or turn screen off, the laptop will always suspend both on battery or while plugged on power. Version-Release number of selected component (if applicable): Version: 1.6.0 Release: 7.fc27 How reproducible: Always reproducible. Steps to Reproduce: 1. Open xfce4-power-manager. 2. Change "When laptop lid is closed:" on the "Laptop lid" section in the "General" tab to anything else besides suspend. 3. Close the laptop lid. Actual results: Laptop always suspend even if the setting was changed to something else. Expected results: Laptop follows the changed settings instead of suspending. Additional info: Hardware used is a ThinkPad X220 running Fedora 27 XFCE installed through netinstall. I changed xscreensaver to light-locker and added "Option TearFree" to a X11 config file, but I believe it doesn't affect xfce4-power-manager behavior. I am also running tlp and added an exception for it on SELinux but I haven't seen it affecting xfce4-power-manager before.
Thanks for the logs. I will take a look and ask for more information if needed.
I wiped my X220 clean today to do some more throughout testing, without tlp, light-locker or any other extra baggage. I am able to confirm that the results are similar to what I reported earlier, with a small caveat: It is only following what it is being set in "On battery:", even when plugged in. Furthermore, I went and edited flags "HandleLidSwitch=suspend" and "HandleLidSwitchDocked=ignore" in "/etc/systemd/logind.conf" and restarted its service, and while it overrides xfce4-power-manager settings, it seems like "HandleLidSwitchDocked" is ignored. I can only conclude that there is some issue into detecting if the laptop is plugged in/docked that is present in Fedora. I also quickly checked if there was a similar issue with other distros (such as Debian and Arch), but they are working fine.
xfce4-power-manager-1.6.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec289f3b63
xfce4-power-manager-1.6.1-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-db7878f368
xfce4-power-manager-1.6.1-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-db7878f368
xfce4-power-manager-1.6.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec289f3b63
1.6.1.1 didn't change a thing, I also tried to regen its config (~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml) just in case by deleting it, still a no go with the original described setup (light-locker), I might test it with xscreensaver later but I doubt it would change a thing. Furthermore, this update added a small bug where xfce4-power-manager reports the battery as fully charged before it hits 100%, it seems to have gone back to normal after I suspended the laptop.
xfce4-power-manager-1.6.1-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
xfce4-power-manager-1.6.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Addendum: Sadly, not fixed, and seems to be an upstream issue: https://bugzilla.xfce.org/show_bug.cgi?id=12756 As a workaround, use mate-power-manager or any other power manager replacement for now.
Finally, after some messing around, I managed to find a workaround for the upstream bug: xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -n -t bool -s false Making it ignore logind does the trick, I believe this command could be run as a scriptlet, otherwise changing the default config file would do the trick too.
I'm having the same problem on Cinnamon Desktop. Might these be related? When plugged in, despite having it set so that a closed lid 'does nothing', it will suspend anyway.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.