Hello,

if the laptop lid is closed, then the laptop is put into standby mode, but the screen is not locked. I.e. after opening the lid, the screen is not locked.

But when the standby button is pressed, the screen is locked and the laptop goes into standby mode.
Could this be a bug in elogind, which does the job of monitoring lid closure?

~$ cat /etc/devuan_version 
chimaera

~$ xfconf-query -c xfce4-power-manager -l -v
/xfce4-power-manager/brightness-switch                  0
/xfce4-power-manager/brightness-switch-restore-on-exit  1
/xfce4-power-manager/critical-power-action              3
/xfce4-power-manager/inactivity-on-battery              46
/xfce4-power-manager/inactivity-sleep-mode-on-battery   1
/xfce4-power-manager/lid-action-on-ac                   1
/xfce4-power-manager/lid-action-on-battery              1
/xfce4-power-manager/lock-screen-suspend-hibernate      true
/xfce4-power-manager/logind-handle-lid-switch           true
/xfce4-power-manager/power-button-action                3
/xfce4-power-manager/show-tray-icon                     false

~$ xfconf-query -c xfce4-session -l -v
/general/FailsafeSessionName          Failsafe
/general/LockCommand                  
/general/PromptOnLogout               false
/general/SessionName                  Default
/sessions/Failsafe/Client0_Command    <<UNSUPPORTED>>
/sessions/Failsafe/Client0_PerScreen  false
/sessions/Failsafe/Client0_Priority   15
/sessions/Failsafe/Client1_Command    <<UNSUPPORTED>>
/sessions/Failsafe/Client1_PerScreen  false
/sessions/Failsafe/Client1_Priority   20
/sessions/Failsafe/Client2_Command    <<UNSUPPORTED>>
/sessions/Failsafe/Client2_PerScreen  false
/sessions/Failsafe/Client2_Priority   25
/sessions/Failsafe/Client3_Command    <<UNSUPPORTED>>
/sessions/Failsafe/Client3_PerScreen  false
/sessions/Failsafe/Client3_Priority   30
/sessions/Failsafe/Client4_Command    <<UNSUPPORTED>>
/sessions/Failsafe/Client4_PerScreen  false
/sessions/Failsafe/Client4_Priority   35
/sessions/Failsafe/Count              5
/sessions/Failsafe/IsFailsafe         true
/shutdown/LockScreen                  true

Thank you!

Kind regards
Klaus

Hello,

where do I place scripts that should be run before suspend and after resume?
My system is running elogind and suspend with

loginctl suspend

works. I think that this is the command that is used when supending with KDE Plasma menu?

Thanks and kind regards
Klaus

Hello,

I have an LDAP setup with Devuan ascii with libpam_ldap and libnss_ldap. "getent group" and "getent passwd" delivers the LDAP groups and users. To get local groups like audio, plugdev etc. assigned to the LDAP users I configured pam_group.so:

cat /etc/security/group.conf:
*;*;%DOMAINUSERS;Al0000-2400;plugdev,audio,cdrom,dialout,floppy,dip,video,netdev

cat /etc/pam.d/common-auth:
...
# here are the per-package modules (the "Primary" block)
auth    required                        pam_group.so use_first_pass
auth    [success=2 default=ignore]    pam_unix.so nullok_secure try_first_pass
auth    [success=1 default=ignore]    pam_ldap.so use_first_pass
...

When I now login to slim login manager with an LDAP user and afterwards check my groups in a terminal I only get the LDAP groups but not the local groups:
~$ groups
STUDENTS DOMAINUSERS 5A 5B 5C 5D 6A 6B 6C 6D 7A 7B 7C 7D 8A 8B 8C 8D 9A 9B 9C 9D 10A 10B 10C 10D 11A 11B 11C 11D 12

When I login with ssh I get the local groups:
~$ groups
STUDENTS dialout cdrom floppy audio dip video plugdev netdev DOMAINUSERS 5A 5B 5C 5D 6A 6B 6C 6D 7A 7B 7C 7D 8A 8B 8C 8D 9A 9B 9C 9D 10A 10B 10C 10D 11A 11B 11C 11D 12

How do I tell slim to honor pam_group?

Thanks!