usually I lock the screen of my openbox sessions (no DE) on demand by running xflock4 .
Today I locked the screen using dm-tool lock , since xflock4 fails.
I don't know when it exactly stopped working. The time frame is between the beginning of last week, until today.
[2022-12-16T13:56:41+0100] [ALPM] upgraded xfce4-session (4.16.0-2 -> 4.18.0-1)
I wonder if it's a bug or if some changes require to re/start something etc..
Here we go!
/usr/bin/xflock4 is a script expecting a value by
xfconf-query -c xfce4-session -p /general/LockCommand
which returns nothing on my machine.
Apart from lightdm on my machine the packages slock and xlockmore are installed and before xflock4 stopped working, it seemingly used xlock -mode blank.
After using xfconf-query to set the wanted value, xflock4 is working again.
xfconf-query -c xfce4-session -p /general/LockCommand -s "xlock -mode blank"
However, I'll rethink to use xflock4 by panel entries or scripts for openbox sessions. Maybe I chose xflock4 years back for portability among Xfce4 and openbox or other sessions. Actually I didn't start a Xfce4 session for years.