Created attachment 6770 Screenshot of settings window Hi! This bug has been reported against the Debian package of 1.4.4, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800890 I have just tried with 1.6.0, and have the same problem. Attached is a screenshot of the XFCE4 Power Manager settings; when I shut the lid on AC power, the system suspends. Best wishes!
I can confirm I am also seeing this issue on the following version of the power manager: xfce4-power-manager 1.4.4-2 Seems like even if both battery and AC power are set to turn off display the power manager suspends when the laptop lid is closed. I believe the suspend is the default for systemd, it seems like the xfce-power-manager settings are being ignored.
This is most likely caused by the light-locker integration. More specifically by xfpm_update_logind_handle_lid_switch in xfpm-settings.c: logind-handle-lid-switch = true when: lock_on_suspend == true and (lid_switch_on_ac == suspend or lid_switch_on_battery == suspend) That means, that xfpm unconditionally removes the handle-lid-switch inhibitor. Instead xfpm should check the power mode (battery/AC) and only remove the inhibitor if it is actually configured to do so for the current power mode. Of course this check must be repeated on every change of the power mode. Test case: On eg. AC mode set the lid close action for battery mode to suspend and for AC mode to eg. lock screen. systemd-inhibit --list shows that the handle-lid-switch inhibitor is removed. Closing the lid in AC mode consequently lets logind handle the event, which defaults to suspend.
Fedora 25 XFCE spin. Power manager version 1.6.0. same problem here.
This is a duplicate of bug 12088. As comment 2 and bug 12088, comment 0 respectively show, xfpm in the current design can not handle a setup were the lid close action is either to lock the screen or to suspend depending on the actual power state (although the ui suggests it).
Confirmed on Xubuntu 18.04, it was also present on Xubuntu 17.10. xfce4-power-manager 1.6.1
*** This bug has been marked as a duplicate of bug 15300 ***