If the setting `/general/LockCommand` is set to `xflock4`, [the script](https://gitlab.xfce.org/xfce/xfce4-session/-/blob/53ef72c40f6afd8170a7f7c37937576773ca8a35/scripts/xflock4) will gladfully call itself until all resources on the host are used. A workaround would be to ignore `$LOCK_CMD` if the resolution of the command is the script itself. I assume something like this would solve the issue, but it is probably too naive. ```sh LOCK_CMD="xflock4" if [ "$(realpath "$0")" = "$(which "$LOCK_CMD")" ]; then LOCK_CMD="" fi ```