Created attachment 6131 Patch to bypass null/blank LockCommand parameter Commit http://git.xfce.org/xfce/xfce4-session/commit/?id=e940818853582290af21bf38d73ee26143d500ad breaks xflock4 functionality if the xfconf LockCommand parameter doesn't exist or is a blank entry. The $lock_cmd >/dev/null 2>&1 && exit will run a blank (empty string) and then exist, never getting to the other items in the list. The fix is to prepend to that command a check to see if the variable is blank: if [ ! -z "$lock_cmd" ]; then $lock_cmd >/dev/null 2>&1 && exit fi Patch attached.
if xfconf is edited to add /general/LockCommand with a valid locker it works .. Yes the patch is necessary ..
Thanks ToZ! Pushed to master in: commit 495aac78058cd78e2d34505af204e72a1b4f19ac Author: Eric Koegel <eric.koegel@gmail.com> Date: Sat Mar 28 06:16:10 2015 +0300 Xflock: bypass null/blank LockCommand parameter (Bug #11764) Commit http://git.xfce.org/xfce/xfce4-session/commit/?id=e940818853582290af21bf38d73ee26143d500ad breaks xflock4 functionality if the xfconf LockCommand parameter doesn't exist or is a blank entry. The $lock_cmd >/dev/null 2>&1 && exit will run a blank (empty string) and then exist, never getting to the other items in the list. Bug report and patch provided by ToZ. http://git.xfce.org/xfce/xfce4-session/commit/?id=495aac78058cd78e2d34505af204e72a1b4f19ac